lkml.org 
[lkml]   [2015]   [Aug]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH v1 3/3] arm64: dts: add Hi6220 mailbox node
From
Date
On 26/08/15 02:25, Haojian Zhuang wrote:
>> Option 1:
>>
>> memory@0 {
>> device_type = "memory";
>> reg = <0x00000000 0x00000000 0x00000000 0x05e00000>,
>> <0x00000000 0x05f00000 0x00000000 0x00eff000>,
>> <0x00000000 0x06e00000 0x00000000 0x0060f000>,
>> <0x00000000 0x07410000 0x00000000 0x38bf0000>;
>> };
>>
>> [snip]
>>
>> Option 2:
>>
>> memory@0 {
>> device_type = "memory";
>> reg = <0x0 0x0 0x0 0x40000000>;
>> };
>>
>> [snip]
>>
>
> I prefer the second one. From my view, memory node should only describe
> the hardware information of memory.

Haven't we already established that, to avoid the risk of UEFI
applications accessing inappropriate memory locations, a (correct) UEFI
implementation must use, and pass to the kernel, a memory map that looks
like option 1?

That being the case why would we want u-boot (or any other similar
bootloader) to pass a memory map that is gratuitously different to the
one supplied by UEFI?


Daniel.


\
 
 \ /
  Last update: 2015-08-27 18:21    [W:0.140 / U:0.104 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site