From: "Ard Biesheuvel" <ard.biesheuvel@linaro.org>
To: Pete Batard <pete@akeo.ie>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>,
"Leif Lindholm" <leif.lindholm@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [edk2-non-osi][PATCH 0/2] Add prerequisite binary files for RPi4 platform
Date: Wed, 11 Dec 2019 15:13:48 +0100 [thread overview]
Message-ID: <CAKv+Gu8QX5RZBRLfg7M5bWw7+BPZJ_nfXzXjSyf=QvbvtaxONQ@mail.gmail.com> (raw)
In-Reply-To: <20191211112400.1872-1-pete@akeo.ie>
On Wed, 11 Dec 2019 at 12:24, Pete Batard <pete@akeo.ie> wrote:
>
> This series of patches adds the binaries we need available to introduce
> Raspberry Pi 4 support.
>
> Similar to the Pi 3, we must have TF-A and Device Tree binaries we can embed.
>
> Pete Batard (2):
> Platforms/RPi4: Add Device Tree
> Platforms/RPi4: Add Trusted Firmware binaries
>
Thanks Pete
Pushed as d580026dbbe8..a2484c34ceba
> Platform/RaspberryPi/RPi4/DeviceTree/License.txt | 340 ++++++++++++++++++++
> Platform/RaspberryPi/RPi4/DeviceTree/Readme.md | 13 +
> Platform/RaspberryPi/RPi4/DeviceTree/bcm2711-rpi-4-b.dtb | Bin 0 -> 40697 bytes
> 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
> 7 files changed, 391 insertions(+)
> create mode 100644 Platform/RaspberryPi/RPi4/DeviceTree/License.txt
> create mode 100644 Platform/RaspberryPi/RPi4/DeviceTree/Readme.md
> create mode 100644 Platform/RaspberryPi/RPi4/DeviceTree/bcm2711-rpi-4-b.dtb
> create mode 100644 Platform/RaspberryPi/RPi4/TrustedFirmware/License.txt
> create mode 100644 Platform/RaspberryPi/RPi4/TrustedFirmware/Readme.md
> create mode 100644 Platform/RaspberryPi/RPi4/TrustedFirmware/bl31_miniuart.bin
> create mode 100644 Platform/RaspberryPi/RPi4/TrustedFirmware/bl31_pl011.bin
>
> --
> 2.21.0.windows.1
>
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
2019-12-11 15:35 ` Pete Batard
2019-12-11 14:13 ` Ard Biesheuvel [this message]
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='CAKv+Gu8QX5RZBRLfg7M5bWw7+BPZJ_nfXzXjSyf=QvbvtaxONQ@mail.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