From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Gaël PORTAY" <gael.portay@gmail.com>
Cc: "Gaël PORTAY" <gael.portay@rtone.fr>,
"Martin Bark" <martin@barkynet.com>,
"Julien Grossholtz" <julien.grossholtz@openest.io>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 0/8] configs/raspberrypi*: install missing dtb
Date: Wed, 17 Jul 2024 23:19:54 +0200 [thread overview]
Message-ID: <20240717231954.6fed9730@windsurf> (raw)
In-Reply-To: <20240716054359.92966-1-gael.portay@rtone.fr>
Hello,
On Tue, 16 Jul 2024 07:43:51 +0200
"Gaël PORTAY" <gael.portay@gmail.com> wrote:
> The last patch moves some configs in the defconfigs and removes some
> comments so the defconfig files look similar and it makes a diff easy.
>
> Question: I am a bit perplex by installing the Raspberry Pi 2 rev 1.2 in
> the raspberrypi2_defconfig since its switched from BCM2836 (cortex-a7)
> to BCM2837 (cortex-a53, the same as pi3 and pizero2w).
>
> I think it makes sense to install its dtb using its board's defconfig
> (rasperrypi2_defconfig) at the cost of "performance" because it loses
> its true architecture.
Should we introduce a raspberry2_64_defconfig?
> Gaël PORTAY (8):
> configs/raspberrypi: install Raspberry Pi rev 1.0 device-tree blob
> configs/raspberrypi2: install Raspberry Pi 2 rev 1.2 device-tree blob
> configs/raspberrypi3_64: install Compute Module 3 device-tree blob
> configs/raspberrypi3_64: remove upstream device-tree blob
> configs/raspberrypi4*: install Raspberry Pi 400 device-tree blob
> configs/raspberrypi4*: install Compute Module 4/4s device-tree blobs
> configs/raspberrypi5: install BCM2712D0 device-tree blob
> configs/raspberrypi*: sort some configs
All applied, thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-07-17 21:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 5:43 [Buildroot] [PATCH 0/8] configs/raspberrypi*: install missing dtb Gaël PORTAY
2024-07-16 5:43 ` [Buildroot] [PATCH 1/8] configs/raspberrypi: install Raspberry Pi rev 1.0 device-tree blob Gaël PORTAY
2024-07-16 5:43 ` [Buildroot] [PATCH 2/8] configs/raspberrypi2: install Raspberry Pi 2 rev 1.2 " Gaël PORTAY
2024-07-16 5:43 ` [Buildroot] [PATCH 3/8] configs/raspberrypi3_64: install Compute Module 3 " Gaël PORTAY
2024-07-17 21:20 ` Thomas Petazzoni via buildroot
2024-07-16 5:43 ` [Buildroot] [PATCH 4/8] configs/raspberrypi3_64: remove upstream " Gaël PORTAY
2024-07-17 21:21 ` Thomas Petazzoni via buildroot
2024-07-16 5:43 ` [Buildroot] [PATCH 5/8] configs/raspberrypi4*: install Raspberry Pi 400 " Gaël PORTAY
2024-07-16 5:43 ` [Buildroot] [PATCH 6/8] configs/raspberrypi4*: install Compute Module 4/4s device-tree blobs Gaël PORTAY
2024-07-16 5:43 ` [Buildroot] [PATCH 7/8] configs/raspberrypi5: install BCM2712D0 device-tree blob Gaël PORTAY
2024-07-16 5:43 ` [Buildroot] [PATCH 8/8] configs/raspberrypi*: sort some configs Gaël PORTAY
2024-07-17 21:19 ` Thomas Petazzoni via buildroot [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-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=20240717231954.6fed9730@windsurf \
--to=buildroot@buildroot.org \
--cc=gael.portay@gmail.com \
--cc=gael.portay@rtone.fr \
--cc=julien.grossholtz@openest.io \
--cc=martin@barkynet.com \
--cc=thomas.petazzoni@bootlin.com \
/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.