From: "Ard Biesheuvel" <ard.biesheuvel@arm.com>
To: Pete Batard <pete@akeo.ie>,
Andrei Warkentin <andrey.warkentin@gmail.com>,
devel@edk2.groups.io
Cc: leif@nuviainc.com, philmd@redhat.com
Subject: Re: [edk2-platforms][PATCH 1/1] RPi3: minor doc fix
Date: Fri, 1 May 2020 12:27:02 +0200 [thread overview]
Message-ID: <92861ebd-328b-6338-84d3-8faa3d2e5cbc@arm.com> (raw)
In-Reply-To: <4c7512da-ed2f-3844-d17f-053e7dc0997a@akeo.ie>
On 5/1/20 11:43 AM, Pete Batard wrote:
> On 2020.04.30 20:24, Andrei Warkentin wrote:
>> Matches the new reality around FDT support (edk2-platform patches).
>>
>> Signed-off-by: Andrei Warkentin <andrey.warkentin@gmail.com>
>> ---
>> Platform/RaspberryPi/RPi3/TrustedFirmware/Readme.md | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/Platform/RaspberryPi/RPi3/TrustedFirmware/Readme.md
>> b/Platform/RaspberryPi/RPi3/TrustedFirmware/Readme.md
>> index 326f5f9..aafbbe9 100644
>> --- a/Platform/RaspberryPi/RPi3/TrustedFirmware/Readme.md
>> +++ b/Platform/RaspberryPi/RPi3/TrustedFirmware/Readme.md
>> @@ -20,13 +20,15 @@ which results in the following memory mapping:
>> 0x00000000 +-----------------+
>> | ROM | BL1
>> 0x00010000 +-----------------+
>> - | DTB | (Loaded by the VideoCore)
>> + | Nothing |
>> 0x00020000 +-----------------+
>> | FIP |
>> 0x00030000 +-----------------+
>> | |
>> | UEFI PAYLOAD |
>> | |
>> + 0x001f0000 +-----------------+
>> + | DTB | (Loaded by the VideoCore)
>> 0x00200000 +-----------------+
>> | Secure SRAM | BL2, BL31
>> 0x00300000 +-----------------+
>>
>
> Reviewed-by: Pete Batard <pete@akeo.ie>
Thanks, but that file does not exist in edk2-platforms.
next prev parent reply other threads:[~2020-05-01 10:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 19:24 [edk2-platforms][PATCH 1/1] RPi3: minor doc fix Andrei Warkentin
2020-05-01 9:43 ` Pete Batard
2020-05-01 10:27 ` Ard Biesheuvel [this message]
2020-05-01 10:29 ` Pete Batard
2020-05-01 10:38 ` Ard Biesheuvel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=92861ebd-328b-6338-84d3-8faa3d2e5cbc@arm.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox