On 11/08/2016 03:32 AM, Cédric Schieli wrote:
2016-11-08 4:14 GMT+01:00 Stephen Warren mailto:swar...@wwwdotorg.org>>:
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
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 both the
memory size and
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 and the blob size [1].
>>
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
>>
>> [1] https://www.raspbe
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 way
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
6 matches
Mail list logo
