From: "Andrei Warkentin" <andrey.warkentin@gmail.com>
To: devel@edk2.groups.io
Cc: ard.biesheuvel@arm.com, leif@nuviainc.com, pete@akeo.ie,
philmd@redhat.com
Subject: [edk2-platforms][PATCH 4/4] RPi3/RPi4: touch up readme's a bit.
Date: Thu, 30 Apr 2020 01:47:46 -0700 [thread overview]
Message-ID: <20200430084746.51455-5-andrey.warkentin@gmail.com> (raw)
In-Reply-To: <20200430084746.51455-1-andrey.warkentin@gmail.com>
Just cleanups to areas I know have gotten a bit stale.
Signed-off-by: Andrei Warkentin <andrey.warkentin@gmail.com>
---
Platform/RaspberryPi/RPi3/Readme.md | 6 ++++--
Platform/RaspberryPi/RPi4/Readme.md | 20 ++++++++++++++++++++
2 files changed, 24 insertions(+), 2 deletions(-)
diff --git a/Platform/RaspberryPi/RPi3/Readme.md b/Platform/RaspberryPi/RPi3/Readme.md
index b756013b..55c6265d 100644
--- a/Platform/RaspberryPi/RPi3/Readme.md
+++ b/Platform/RaspberryPi/RPi3/Readme.md
@@ -173,7 +173,7 @@ Known issues:
## USB
- USB1 BBB mass storage devices untested (USB2 and USB3 devices are fine).
-- USB1 CBI mass storage devices don't work (e.g. HP FD-05PUB floppy).
+- Some USB1 CBI (e.g. UFI floppy) mass storage devices may not work.
## ACPI
@@ -187,4 +187,6 @@ install a kernel that relies on Device Tree rather than ACPI.
## Missing Functionality
- Network booting via onboard NIC.
-- Ability to switch UART use to PL011.
+- SPCR hardcodes UART type to miniUART, and thus will not expose correct
+ (PL011) UART on CM3 and Pi2B or if DT overlays to switch UART are used
+ on Pi 3B/3B+/3A+.
diff --git a/Platform/RaspberryPi/RPi4/Readme.md b/Platform/RaspberryPi/RPi4/Readme.md
index 1f4ed001..c1ecfc99 100644
--- a/Platform/RaspberryPi/RPi4/Readme.md
+++ b/Platform/RaspberryPi/RPi4/Readme.md
@@ -121,3 +121,23 @@ An `RtcEpochSeconds` NVRAM variable is used to store the boot time.
This should allow you to set whatever date/time you want using the Shell date and
time commands. While in UEFI or HLOS, the time will tick forward.
`RtcEpochSeconds` is not updated on reboots.
+
+## USB
+
+This UEFI supports both the USB3 xHCI ports (front ports), and the Pi 3-style
+DesignWare USB2 controller via the Type-C port (host only).
+
+The following only apply to the Type-C port:
+- USB1 BBB mass storage devices untested (USB2 and USB3 devices are fine).
+- Some USB1 CBI (e.g. UFI floppy) mass storage devices may not work.
+
+## ACPI
+
+OS support for ACPI description of Pi-specific devices is still in development. Not
+all functionality may be available.
+
+## Missing Functionality
+
+- Network booting via onboard NIC.
+- SPCR hardcodes type to PL011, and thus will not expose correct
+ (miniUART) UART if DT overlays to switch UART are used on Pi 4B.
\ No newline at end of file
--
2.17.1
next prev parent reply other threads:[~2020-04-30 8:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 8:47 [edk2-platforms][PATCH 0/4] extend RPi3 to support 3A+, 2B (v1.2) and CM3 Andrei Warkentin
2020-04-30 8:47 ` [edk2-platforms][PATCH 1/4] RPi3/RPi4: document 3A+ support Andrei Warkentin
2020-04-30 8:47 ` [edk2-platforms][PATCH 2/4] RPi3: add support for the v1.2 Pi 2B Andrei Warkentin
2020-04-30 8:47 ` [edk2-platforms][PATCH 3/4] RPi3: add support for Compute Module 3 Andrei Warkentin
2020-04-30 8:50 ` Ard Biesheuvel
2020-04-30 8:47 ` Andrei Warkentin [this message]
2020-04-30 8:57 ` [edk2-platforms][PATCH 0/4] extend RPi3 to support 3A+, 2B (v1.2) and CM3 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=20200430084746.51455-5-andrey.warkentin@gmail.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