public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Pete Batard" <pete@akeo.ie>
To: devel@edk2.groups.io
Cc: ard.biesheuvel@arm.com, leif@nuviainc.com, awarkentin@vmware.com
Subject: [edk2-platforms][PATCH 2/2] Platform/RPi: Fix Readme issues
Date: Tue, 21 Apr 2020 12:30:15 +0100	[thread overview]
Message-ID: <20200421113015.13936-2-pete@akeo.ie> (raw)
In-Reply-To: <20200421113015.13936-1-pete@akeo.ie>

* device_tree_address/end was incorrect for RPi3.
* Link to TF-A Readme.md in non-osi was broken.
* RPi4 now uses TF-A binaries built from official source.

Signed-off-by: Pete Batard <pete@akeo.ie>
---
 Platform/RaspberryPi/RPi3/Readme.md | 15 ++++++++-------
 Platform/RaspberryPi/RPi4/Readme.md | 13 +++++--------
 2 files changed, 13 insertions(+), 15 deletions(-)

diff --git a/Platform/RaspberryPi/RPi3/Readme.md b/Platform/RaspberryPi/RPi3/Readme.md
index 58c0124ef75e..05f498ee50a7 100644
--- a/Platform/RaspberryPi/RPi3/Readme.md
+++ b/Platform/RaspberryPi/RPi3/Readme.md
@@ -54,8 +54,8 @@ Build instructions from the top level edk2-platforms Readme.md apply.
   ```
   Additionally, if you want to use PL011 instead of the miniUART, you can add the lines:
   ```
-  device_tree_address=0x20000
-  device_tree_end=0x30000
+  device_tree_address=0x10000
+  device_tree_end=0x20000
   device_tree=bcm2710-rpi-3-b[-plus].dtb
   dtoverlay=miniuart-bt
   ```
@@ -67,13 +67,14 @@ you may also be able to boot from a FAT32 USB driver rather than uSD.
 
 # Notes
 
-## ARM Trusted Firmware (ATF)
+## ARM Trusted Firmware (TF-A)
 
-The ATF binaries being used were compiled from the latest ATF source.
-No aleration to the official source have been applied.
+The TF-A binary files were compiled from the latest TF-A release.
+No aleration to the official source has been applied.
 
-For more details on the ATF compilation, see the [Readme](./TrustedFirmware/Readme.md)
-in the `TrustedFirmware/` directory.
+For more details on the TF-A compilation, see the relevant
+[Readme](https://github.com/tianocore/edk2-non-osi/blob/master/Platform/RaspberryPi/RPi3/TrustedFirmware/Readme.md)
+in the `TrustedFirmware/` directory from `edk2-non-osi`.
 
 ## Custom Device Tree
 
diff --git a/Platform/RaspberryPi/RPi4/Readme.md b/Platform/RaspberryPi/RPi4/Readme.md
index e2f0d6986bfd..fa9b31464d58 100644
--- a/Platform/RaspberryPi/RPi4/Readme.md
+++ b/Platform/RaspberryPi/RPi4/Readme.md
@@ -63,15 +63,12 @@ Build instructions from the top level edk2-platforms Readme.md apply.
 
 ## ARM Trusted Firmware (TF-A)
 
-The TF-A binaries were compiled from a TF-A source over which 2 serial-output related
-patches were applied, the first one to fix the miniUART baud rate not being properly
-set to 115200 bauds with recent versions of `start4.elf` and the second one to allow
-the use of the PL011 UART.
+The TF-A binary was compiled from the latest TF-A release.
+No aleration to the official source has been applied.
 
-No other alterations to the official source have been applied.
-
-For more details on the TF-A compilation, see the [Readme](./TrustedFirmware/Readme.md)
-in the `TrustedFirmware/` directory.
+For more details on the TF-A compilation, see the relevant
+[Readme](https://github.com/tianocore/edk2-non-osi/blob/master/Platform/RaspberryPi/RPi4/TrustedFirmware/Readme.md)
+in the `TrustedFirmware/` directory from `edk2-non-osi`.
 
 ## Device Tree
 
-- 
2.21.0.windows.1


  reply	other threads:[~2020-04-21 11:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21 11:30 [edk2-platforms][PATCH 1/2] Platform/RPi4: Update DSC to reflect switch to single TF-A binary Pete Batard
2020-04-21 11:30 ` Pete Batard [this message]
2020-04-21 13:04 ` 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=20200421113015.13936-2-pete@akeo.ie \
    --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