From: "Pete Batard" <pete@akeo.ie>
To: devel@edk2.groups.io
Cc: ard.biesheuvel@linaro.org, leif.lindholm@linaro.org
Subject: [edk2-platforms: PATCH 0/2] Platform/RPi3 improve boot order and add custom freqs
Date: Tue, 2 Jul 2019 17:13:39 +0100 [thread overview]
Message-ID: <20190702161341.2652-1-pete@akeo.ie> (raw)
The following 2 patches update the Raspberry Pi 3 platform to:
- Remove UEFI Shell as default boot target, to instead default to SD then USB,
which is the what most users of the UEFI firmware are likely to expect.
- Add the ability to set a custom CPU frequency [100 - 1600 MHz] instead
of only allowing to pick from a limited set of default values.
Regards,
/Pete
Pete Batard (2):
Platform/RPi3: Set the boot option of UEFI Shell as non-active
Platform/Rpi3: Add custom CPU frequency support
Platform/RaspberryPi/RPi3/Drivers/ConfigDxe/ConfigDxe.c | 13 +++++++++++-
Platform/RaspberryPi/RPi3/Drivers/ConfigDxe/ConfigDxe.inf | 1 +
Platform/RaspberryPi/RPi3/Drivers/ConfigDxe/ConfigDxeHii.uni | 4 ++++
Platform/RaspberryPi/RPi3/Drivers/ConfigDxe/ConfigDxeHii.vfr | 22 ++++++++++++++++++++
Platform/RaspberryPi/RPi3/Drivers/RpiFirmwareDxe/RpiFirmwareDxe.c | 4 +++-
Platform/RaspberryPi/RPi3/Include/Protocol/RpiFirmware.h | 3 ++-
Platform/RaspberryPi/RPi3/Library/PlatformBootManagerLib/PlatformBm.c | 2 +-
Platform/RaspberryPi/RPi3/RPi3.dec | 17 ++++++++-------
Platform/RaspberryPi/RPi3/RPi3.dsc | 1 +
Platform/RaspberryPi/RPi3/Readme.md | 6 +++---
10 files changed, 58 insertions(+), 15 deletions(-)
--
2.21.0.windows.1
next reply other threads:[~2019-07-02 16:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 16:13 Pete Batard [this message]
2019-07-02 16:13 ` [edk2-platforms: PATCH 1/2] Platform/RPi3: Set the boot option of UEFI Shell as non-active Pete Batard
2019-07-03 11:43 ` Leif Lindholm
2019-07-02 16:13 ` [edk2-platforms: PATCH 2/2] Platform/Rpi3: Add custom CPU frequency support Pete Batard
2019-07-03 11:42 ` Leif Lindholm
2019-07-03 12:09 ` Pete Batard
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=20190702161341.2652-1-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