From: "Leif Lindholm" <leif.lindholm@linaro.org>
To: Pete Batard <pete@akeo.ie>
Cc: devel@edk2.groups.io, ard.biesheuvel@linaro.org, philmd@redhat.com
Subject: Re: [edk2-non-osi][PATCH 2/2] Platforms/RPi4: Add Trusted Firmware binaries
Date: Wed, 11 Dec 2019 14:14:44 +0000 [thread overview]
Message-ID: <20191211141443.GB7359@bivouac.eciton.net> (raw)
In-Reply-To: <20191211112400.1872-3-pete@akeo.ie>
On Wed, Dec 11, 2019 at 11:24:00 +0000, Pete Batard wrote:
> Similar to what is the case with the Raspberry Pi 3, the Raspberry Pi
> 4 UEFI firmware requires the provision of a Trusted Firmware binary
> (TF-A).
>
> The binary is built for a dtb base address of 0x00020000 and a UEFI
> payload base address of 0x00030000.
>
> Binaries are built using a custom version of TF-A (the source of which
> is documented in the Readme), since the official repository is missing
> a fix to get proper baudrate when using a recent version of start4.elf,
> as we as the ability to switch between PL011 and mini UART. We are
> currently working with TF-A to upstream both these fixes so that we can
> switch to binaries built from official source at a later date.
>
> In order to provide the ability to switch serial I/O controllers, a
> feature we will be adding to the RPi4 UEFI Firmware, and not lose TF-A
> output, two binaries are provided, one for mini UART output and one for
> PL011 output.
>
> Signed-off-by: Pete Batard <pete@akeo.ie>
> ---
> Platform/RaspberryPi/RPi4/TrustedFirmware/License.txt | 26 ++++++++++++++++++++
> Platform/RaspberryPi/RPi4/TrustedFirmware/Readme.md | 12 +++++++++
> Platform/RaspberryPi/RPi4/TrustedFirmware/bl31_miniuart.bin | Bin 0 -> 41072 bytes
> Platform/RaspberryPi/RPi4/TrustedFirmware/bl31_pl011.bin | Bin 0 -> 41072 bytes
> 4 files changed, 38 insertions(+)
>
> new file mode 100644
> index 000000000000..7f1749dfc3a0
> --- /dev/null
> +++ b/Platform/RaspberryPi/RPi4/TrustedFirmware/Readme.md
> @@ -0,0 +1,12 @@
> +ARM Trusted Firmware for Raspberry Pi 4
> +=======================================
> +
> +The `bl31_#####.bin` TF-A binaries found in this repository were built on a Debian 10.2 system
> +from https://github.com/pbatard/arm-trusted-firmware/tree/pi4 (pi4 branch) using the command:
> +
> +```
> +make PLAT=rpi4 RPI3_PRELOADED_DTB_BASE=0x20000 PRELOADED_BL33_BASE=0x30000 SUPPORT_VFP=1 [RPI3_USE_PL011_UART=1] DEBUG=0 all
> +```
> +
> +The only difference between these firmwares is that the `RPI3_USE_PL011_UART=1` option was added
> +to build `bl31_pl011.bin` so that it uses PL011 for serial output rather than the "mini UART".
Sanity check: do the build commands still use RPI3_ options for rpi4?
Best Regards,
Leif
next prev parent reply other threads:[~2019-12-11 14:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 11:23 [edk2-non-osi][PATCH 0/2] Add prerequisite binary files for RPi4 platform Pete Batard
2019-12-11 11:23 ` [edk2-non-osi][PATCH 1/2] Platforms/RPi4: Add Device Tree Pete Batard
2019-12-11 11:24 ` [edk2-non-osi][PATCH 2/2] Platforms/RPi4: Add Trusted Firmware binaries Pete Batard
2019-12-11 14:14 ` Leif Lindholm [this message]
2019-12-11 15:35 ` Pete Batard
2019-12-11 14:13 ` [edk2-non-osi][PATCH 0/2] Add prerequisite binary files for RPi4 platform 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=20191211141443.GB7359@bivouac.eciton.net \
--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