On 08/08/2012 12:30 PM, Rob Herring wrote:
> David Marlin <dmarlin@...> writes:
>>
>> Some vendors already provide U-Boot environment variables for the load
>> addresses, and some for the load commands themselves, but I have not
>> found much consistency between them. One example is the Genesi Efika MX
>> (mx51), which provides:
>>
>> ${loadcmd}
>> ${kerneladdr}
>> ${ramdiskaddr}
>>
>> By providing the kernel and initrd U-Boot images in a boot.scr, you can
>> load and boot the desired kernel with no other board specific knowledge
>> (specific addresses or devices).
>>
>> Highbank provides some similar load address definitions, but with
>> different names, i.e.,
>>
>> ${ramdisk_addr_r}
>> ${kernel_addr_r}
>> ${fdt_addr_r}
>>
>
> Just FYI, these are already the standard, documented variable names.
Interesting. The U-Boot README isn't very strongly worded about those
being standard though:
> *Note* - these variables don't have to be defined for all boards, some
> boards currenlty use other variables for these purposes, and some
> boards use these variables for other purposes.
>
> Image File Name RAM Address Flash Location
> ----- --------- ----------- --------------
> u-boot u-boot u-boot_addr_r u-boot_addr
> Linux kernel bootfile kernel_addr_r kernel_addr
> device tree blob fdtfile fdt_addr_r fdt_addr
> ramdisk ramdiskfile ramdisk_addr_r ramdisk_addr
Perhaps we could make that wording more forceful and less "but you can
do whatever you want"?
_______________________________________________
cross-distro mailing list
[email protected]
http://lists.linaro.org/mailman/listinfo/cross-distro
