* Karsten Merker <mer...@debian.org> [2016-01-04 08:25]:
> > 2) Kernel/ramdisk and uImages
> >
> > At the moment, armhf requires users to append the DTB and generate an
> > uImage. Obviously, the same approach would work for these NAS devices
> > but I'd like to make it as easy for users as possible. So I was
> > thinking of generating uImage/uInitrd files as part of the d-i
> > process. But if I do it for these NAS devices, you could argue we
> > should do it for all devices and that would be a lot of images. So,
> > again, I wanted to hear what people think.
>
> For a large part of the supported armhf devices, appending the dtb to the
> kernel and generating uImages isn't necessary because they have a modern
> enough u-boot that is able to directly boot zImages, initrds and separate
> dtbs ("bootz" command).
Good point. The device I'm interested in doesn't have bootz but it
can load a DTB via bootm.
Maybe I'll just ask users to create their own uImage/uInitrd for now.
If that causes problems for users, I could always create
network-console/seagate/ later with an uImage and uInitrd.
Any input on 1)?
--
Martin Michlmayr
http://www.cyrius.com/
