Bug#626031: debian-kernel-handbook: please support U-Boot format images.
2011/5/8 Martin Michlmayr <firstname.lastname@example.org>:
> * Hector Oron <email@example.com> [2011-05-08 08:10]:
>> Adding support for U-Boot image format ('uImage' kernel target) in
>> official kernel packages seem to me the right thing to do, it would
> This was suggested before but there are some reasons why I don't
> believe it will work:
> - We need to hardcode the machine ID into the kernel and the machine
> ID depends on a particular device, so shipping a uImage rather than
> a normal kernel file will just make it harder.
I think machine_ID and kernel_format (uImage|vmlinuz|vmlinux) could
easily be fields in the architecture config files (defines).
Having a kernel task that overrides machine ID (when needed) does not
seem to be a complicated task either. OTOH, we
simplify `debian-installer` and `flash-kernel` (where code is
duplicated), plus we avoid to play with create, upgrade, delete
> - Some machines require different uImage settings (load address, etc).
> For example, the mv2120 doesn't use a normal uImage but a
> multi-boot uImage.
What's a multi-boot uImage?
Héctor Orón -.. . -... .. .- -. -.. . ...- . .-.. --- .--. . .-.
PS.- I have just built an uImage for tegra device and linux kernel
have all the needed information,
why Debian Linux kernel is unable to do the same?
zumbi@ts01:~/linux-2.6.39-rc6$ make uImage
make: `include/generated/mach-types.h' is up to date.
Kernel: arch/arm/boot/Image is ready
Kernel: arch/arm/boot/zImage is ready
Image Name: Linux-2.6.39-rc6
Created: Sun May 8 09:47:21 2011
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2147104 Bytes = 2096.78 kB = 2.05 MB
Load Address: 00008000
Entry Point: 00008000
Image arch/arm/boot/uImage is ready
"Our Sun unleashes tremendous flares expelling hot gas into the Solar
System, which one day will disconnect us."
-- Day DVB-T stop working nicely
Video flare: http://antwrp.gsfc.nasa.gov/apod/ap100510.html