From: Tom Rini <trini@konsulko.com>
To: Bruno Leite <brunosampaioleite@gmail.com>
Cc: u-boot@lists.denx.de, ravi@prevas.dk, probinson@gmail.com,
Matthias Brugger <mbrugger@suse.com>,
clast@prevas.dk, Bruno Leite <brule@prevas.dk>,
Peter Robinson <pbrobinson@gmail.com>
Subject: Re: [PATCH 0/2] Add rpi5 specific defconfig
Date: Fri, 2 May 2025 08:40:31 -0600 [thread overview]
Message-ID: <20250502144031.GT1261075@bill-the-cat> (raw)
In-Reply-To: <20250502113556.134731-1-brunosampaioleite@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 746 bytes --]
On Fri, May 02, 2025 at 01:34:33PM +0200, Bruno Leite wrote:
> From: Bruno Leite <brule@prevas.dk>
>
>
> Currently rpi5 uses a generic rpi_arm64_defconfig file that builds rpi4
> devicetree. Add a defconfig that is specific to the rpi5 building the
> now available upstream dts for that board. The defconfig makes use of
> defconfig including that is now available and only changes the DTS
> related config.
>
> It is also necessary to add a more specific u-boot.dtsi to rpi5, since
> due to the ARCH_BCM283X config it will try to build the
> bcm283x-u-boot.dtsi and break.
My question is, can we not adjust rpi_arm64_defconfig to be generic
enough and not have a problem on Pi 5 due to the default device tree?
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2025-05-02 14:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-02 11:34 [PATCH 0/2] Add rpi5 specific defconfig Bruno Leite
2025-05-02 11:34 ` [PATCH 1/2] arm64: dts: rpi5: add rpi5 u-boot.dtsi Bruno Leite
2025-05-02 11:34 ` [PATCH 2/2] configs: rpi5: add rpi5 specific defconfig Bruno Leite
2025-05-02 14:40 ` Tom Rini [this message]
2025-05-05 8:40 ` [PATCH 0/2] Add " Bruno Leite
2025-05-05 9:45 ` Rasmus Villemoes
2025-05-05 13:48 ` Tom Rini
2025-05-05 20:19 ` Mark Kettenis
2025-05-05 21:28 ` Tom Rini
2025-05-06 7:30 ` Rasmus Villemoes
2025-05-06 17:52 ` Tom Rini
2025-06-15 11:05 ` Peter Robinson
2025-06-18 12:16 ` Rasmus Villemoes
2025-06-15 11:02 ` Peter Robinson
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-all 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=20250502144031.GT1261075@bill-the-cat \
--to=trini@konsulko.com \
--cc=brule@prevas.dk \
--cc=brunosampaioleite@gmail.com \
--cc=clast@prevas.dk \
--cc=mbrugger@suse.com \
--cc=pbrobinson@gmail.com \
--cc=probinson@gmail.com \
--cc=ravi@prevas.dk \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.