Re: [U-Boot] [PATCH v2] rpi: passthrough of the firmware provided FDT blob

2016-11-08 Thread Stephen Warren
On 11/08/2016 03:32 AM, Cédric Schieli wrote: 2016-11-08 4:14 GMT+01:00 Stephen Warren >: Please note that for this to work the U-Boot binary must be tagged with a recent version of the mkknlimg script found in the Rasperry

Re: [U-Boot] [PATCH v2] rpi: passthrough of the firmware provided FDT blob

2016-11-08 Thread Stephen Warren
On 11/08/2016 04:50 AM, Jonathan Liu wrote: On 8 November 2016 at 14:14, Stephen Warren wrote: On 11/07/2016 07:44 AM, Cédric Schieli wrote: Raspberry firmware used to pass a FDT blob at a fixed address (0x100), but this is not true anymore. The address now depends on

Re: [U-Boot] [PATCH v2] rpi: passthrough of the firmware provided FDT blob

2016-11-08 Thread Jonathan Liu
Hi Stephen, On 8 November 2016 at 14:14, Stephen Warren wrote: > On 11/07/2016 07:44 AM, Cédric Schieli wrote: >> >> Raspberry firmware used to pass a FDT blob at a fixed address (0x100), >> but this is not true anymore. The address now depends on both the >> memory size

Re: [U-Boot] [PATCH v2] rpi: passthrough of the firmware provided FDT blob

2016-11-08 Thread Cédric Schieli
2016-11-08 4:14 GMT+01:00 Stephen Warren : > Please note that for this to work the U-Boot binary must be tagged >> with a recent version of the mkknlimg script found in the Rasperry >> Fundation's kernel tree: >> >> /scripts/mkknlimg --dtok /u-boot.bin /boot/u-boot.bin >>

Re: [U-Boot] [PATCH v2] rpi: passthrough of the firmware provided FDT blob

2016-11-07 Thread Stephen Warren
On 11/07/2016 07:44 AM, Cédric Schieli wrote: Raspberry firmware used to pass a FDT blob at a fixed address (0x100), but this is not true anymore. The address now depends on both the memory size and the blob size [1]. If one wants to passthrough this FDT blob to the kernel, the most reliable

[U-Boot] [PATCH v2] rpi: passthrough of the firmware provided FDT blob

2016-11-07 Thread Cédric Schieli
Raspberry firmware used to pass a FDT blob at a fixed address (0x100), but this is not true anymore. The address now depends on both the memory size and the blob size [1]. If one wants to passthrough this FDT blob to the kernel, the most reliable way is to save its address from the r2/x0 register