From: "Ard Biesheuvel" <ard.biesheuvel@arm.com>
To: Andrei Warkentin <andrey.warkentin@gmail.com>, devel@edk2.groups.io
Cc: leif@nuviainc.com, pete@akeo.ie, philmd@redhat.com
Subject: Re: [edk2-platforms][PATCH 0/2] Fixing FDT handling on Pi 3
Date: Fri, 1 May 2020 12:30:26 +0200 [thread overview]
Message-ID: <6f6ce885-acdf-5c74-f07e-d53d78b6188c@arm.com> (raw)
In-Reply-To: <20200430191901.89372-1-andrey.warkentin@gmail.com>
On 4/30/20 9:18 PM, Andrei Warkentin wrote:
> Dear all,
>
> This patch set finishes what I started with the Pi 4 fix for
> the regression seen with newer VideoCore firmware, where a
> device tree passed via config.txt would not be detected by UEFI.
>
> This makes VPU-passed FDT work again on Pi 3 variants. This also
> cleans up the docs around correctly using FDT, hopefully solving
> some of the frustrations seem around using this correctly.
>
> Andrei Warkentin (2):
> RPi3/RPi4: fix RPi 3 VPU-passed FDT handling by unifying with RPi4
> implementation
> RPi: update Pi3 and Pi4 readmes with correct info on FDT handling
>
Pushed as 40f2f135eb7c..defef0562115 (with the typos fixed)
Thanks!
prev parent reply other threads:[~2020-05-01 10:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 19:18 [edk2-platforms][PATCH 0/2] Fixing FDT handling on Pi 3 Andrei Warkentin
2020-04-30 19:19 ` [edk2-platforms][PATCH 1/2] RPi3/RPi4: fix RPi 3 VPU-passed FDT handling by unifying with RPi4 implementation Andrei Warkentin
2020-05-01 9:35 ` Pete Batard
2020-04-30 19:19 ` [edk2-platforms][PATCH 2/2] RPi: update Pi3 and Pi4 readmes with correct info on FDT handling Andrei Warkentin
2020-05-01 9:43 ` Pete Batard
2020-05-01 10:30 ` 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=6f6ce885-acdf-5c74-f07e-d53d78b6188c@arm.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