On fredag 28 april 2006 00.12, Wolfgang Denk wrote:
[linuxppc-dev removed, this is off topic there.]
In message 44513DC1.8040608@orkun.us you wrote:
How would you like to handle the case when dts is packed into multi-image file? Is bootm going to assume that the 3rd Image is dts?
With Ramdisk: kernel is 1st, ramdisk is 2nd, and dts is an optional 3rd file. Without ramdisk: kernel is 1st, and dts is an optional 2nd file.
The image type will be used to find out what is what.
Since dts is tightly coupled to kernel I would prefer something like:
bootm <kernel_addr>[:<dts_addr>] <ramdisk_addr>
That would be an option, too, but I think my proposal is easier to remember, especially when thinking of the multi-file image case.
Hmm... ramdisk_addr (initrd) Isn't the dts supposed to have some file structure?
Suppose we do not have a ramdisk then we could create a ramdisk containing dts information.
If we have a ramdisk couldn't it be patched to contain dts information?
I know to little about this ramdisk will it be discarded to early? Does it have to contain something U-Boot can not provide if used?
/RogerL