[U-Boot-Users] Re: FT u-boot shim
listmember at orkun.us
Thu Apr 27 23:55:13 CEST 2006
Wolfgang Denk wrote:
> In message <D358E665-60E4-48C0-82FD-7A1C16DAF00C at kernel.crashing.org> you wrote:
>> The problem is that there are somethings that u-boot knows that needs
>> to go into the blob (memory size, boot args, initrd info,
>> frequencies, etc.)
> Yes. Can we append auch variable data to the fixed part of the dts?
>> How would we distinguish the bootm command that takes a blob versus
>> the ones we have today?
> Arg count. For example:
> OLD: bootm <kernel_addr>
> or bootm <kernel_addr> <ramdisk_addr>
> NEW: bootm <kernel_addr> - <dts_addr>
> or bootm <kernel_addr> <ramdisk_addr> <dts_addr>
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?
Since dts is tightly coupled to kernel I would prefer something like:
bootm <kernel_addr>[:<dts_addr>] <ramdisk_addr>
More information about the U-Boot