[U-Boot] [PATCH 20/20] tegra: config: nyan-big: Add options required by Chrome OS boot

Simon Glass
2015-05-13T13:56:50Z

Hi Stephen,

On 25 February 2015 at 16:31, Stephen Warren <swarren@wwwdotorg.org> wrote:
> On 02/17/2015 03:29 PM, Simon Glass wrote:
>>
>> We need to match the device tree in the FIT with the U-Boot model so we
>> can automatically select the right device tree. Also adjust the load
>> address
>> so that the device tree is not in the way when a zImage kernel tries to
>> extract itself.
>
>
> We don't tend to use LOADADDR in any of the default boot scripts any more.
> Rather, we explicitly load files to a "semantic" location indicated by one
> of the following variables in tegra124-common.h:
>
> #define MEM_LAYOUT_ENV_SETTINGS \
> "scriptaddr=0x90000000\0" \
> "pxefile_addr_r=0x90100000\0" \
> "kernel_addr_r=0x81000000\0" \
> "fdt_addr_r=0x82000000\0" \
> "ramdisk_addr_r=0x82100000\0"
>
> Perhaps the ChromeOS boot scripts could be adjusted to use one/some of those
> variables?
>
> If the value of CONFIG_LOADADDR isn't appropriate, perhaps we should fix it
> for all Tegra SoCs/boards?

I forgot about this comment sorry. I had problems with the image
overwriting itself. It is a bzImage inside a FIT so doesn't use the
proper FIT decompression.

Anyway I'd like to clarify what is meant by kernel_addr_r. Is that
where the FIT is loaded or where the kernel will decompress to, or
something else?

Regards,
Simon