On 06/09/2019 13.58, Matthias Brugger wrote:
>
> On 06/09/2019 14:11, Alexander Graf wrote:
>> On 06.09.19 13:56, matthias@kernel.org wrote:
>>> From: Matthias Brugger
>>>
>>> When booting through the efi stub, the memory map get's created by
>>> reading the dram bank information. Depending on
On 06/09/2019 15:03, Alexander Graf wrote:
>
> On 06.09.19 14:58, Matthias Brugger wrote:
>>
>> On 06/09/2019 14:11, Alexander Graf wrote:
>>> On 06.09.19 13:56, matthias@kernel.org wrote:
From: Matthias Brugger
When booting through the efi stub, the memory map get's created
On 06.09.19 14:58, Matthias Brugger wrote:
On 06/09/2019 14:11, Alexander Graf wrote:
On 06.09.19 13:56, matthias@kernel.org wrote:
From: Matthias Brugger
When booting through the efi stub, the memory map get's created by
reading the dram bank information. Depending on the version of th
On 06/09/2019 14:11, Alexander Graf wrote:
>
> On 06.09.19 13:56, matthias@kernel.org wrote:
>> From: Matthias Brugger
>>
>> When booting through the efi stub, the memory map get's created by
>> reading the dram bank information. Depending on the version of the RPi4
>> this information chan
On 06.09.19 13:56, matthias@kernel.org wrote:
From: Matthias Brugger
When booting through the efi stub, the memory map get's created by
reading the dram bank information. Depending on the version of the RPi4
this information changes. Read the device tree to initialize the dram
bank data st
From: Matthias Brugger
When booting through the efi stub, the memory map get's created by
reading the dram bank information. Depending on the version of the RPi4
this information changes. Read the device tree to initialize the dram
bank data structure. This way the kernel is able to access the wh
6 matches
Mail list logo