Re: [U-Boot] [PATCH 1/2] ARM: rpi: update memory layout env. var. documentation

Hi Stephen, Looks good to me then. I wasn't sure how U-Boot was typically used on the RPi. Regards, Jonathan On Sunday, 7 February 2016, Stephen Warren wrote: > On 02/06/2016 12:30 AM, Jonathan Liu wrote: > > Hi Stephen, > > > > I actually read the DT loaded by RPi's

Re: [U-Boot] [PATCH 1/2] ARM: rpi: update memory layout env. var. documentation

On 02/06/2016 12:30 AM, Jonathan Liu wrote: > Hi Stephen, > > I actually read the DT loaded by RPi's binary firmware on an RPi 2 in a > U-Boot script: > fdt addr ${fdt_addr_r} && fdt get value bootargs /chosen bootargs > fatload mmc 0:1 ${kernel_addr_r} uImage > bootm ${kernel_addr_r} -

[U-Boot] [PATCH 1/2] ARM: rpi: update memory layout env. var. documentation

Hi Stephen, I actually read the DT loaded by RPi's binary firmware on an RPi 2 in a U-Boot script: fdt addr ${fdt_addr_r} && fdt get value bootargs /chosen bootargs fatload mmc 0:1 ${kernel_addr_r} uImage bootm ${kernel_addr_r} - ${fdt_addr_r} Essentially this loads the kernel with the same

[U-Boot] [PATCH 1/2] ARM: rpi: update memory layout env. var. documentation

Update rpi-common.h's documentation that describes the rationale for choosing various addresses for standardized variables used by boot scripts. This comment was correct when written, but not updated when some of the values were changed. Fixes: 14006a567105 ("rpi: set fdt_addr_r to 0x0100 to