From: "Leif Lindholm" <leif.lindholm@linaro.org>
To: Pete Batard <pete@akeo.ie>
Cc: devel@edk2.groups.io, ard.biesheuvel@linaro.org
Subject: Re: [edk2-non-osi PATCHv2 1/1] Platform/RaspberryPi/RPi3: Use official Device Tree binaries
Date: Mon, 16 Sep 2019 18:47:56 +0100 [thread overview]
Message-ID: <20190916174756.GC13575@bivouac.eciton.net> (raw)
In-Reply-To: <20190915214952.3212-2-pete@akeo.ie>
On Sun, Sep 15, 2019 at 10:49:52PM +0100, Pete Batard wrote:
> With commit 5f003136c2bf86620c0caaef0ad146b5e7fd2f6b having been applied to
> edk2-platforms, we can use the official Raspberry Pi 3 Device Trees from
> https://github.com/raspberrypi/firmware/tree/master/boot, as the FdtDxe
> driver for that platform can insert missing elements, if required.
>
> This patch replaces the existing dtbs with the most recent official ones
> and also removes the custom dts' from which previous dtbs were produced.
>
> Signed-off-by: Pete Batard <pete@akeo.ie>
Reviewed-by: Leif Lindholm <leif.lindholm@linaro.org>
Pushed as 2120cca51851.
Thanks!
> ---
> Platform/RaspberryPi/RPi3/DeviceTree/Readme.md | 14 +
> Platform/RaspberryPi/RPi3/DeviceTree/bcm2710-rpi-3-b-plus.dtb | Bin 25617 -> 27082 bytes
> Platform/RaspberryPi/RPi3/DeviceTree/bcm2710-rpi-3-b-plus.dts | 1263 --------------------
> Platform/RaspberryPi/RPi3/DeviceTree/bcm2710-rpi-3-b.dtb | Bin 25354 -> 26463 bytes
> Platform/RaspberryPi/RPi3/DeviceTree/bcm2710-rpi-3-b.dts | 1259 -------------------
> 5 files changed, 14 insertions(+), 2522 deletions(-)
prev parent reply other threads:[~2019-09-16 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-15 21:49 [edk2-non-osi PATCHv2 0/1] Platform/RaspberryPi/RPi3: Use official Device Tree binaries Pete Batard
2019-09-15 21:49 ` [edk2-non-osi PATCHv2 1/1] " Pete Batard
2019-09-16 17:47 ` Leif Lindholm [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=20190916174756.GC13575@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