From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@buildroot.org
Cc: Martin Bark <martin@barkynet.com>,
Julien Grossholtz <julien.grossholtz@openest.io>
Subject: Re: [Buildroot] [PATCH 1/3] board/raspberry: handle dtb overlays for all variants
Date: Mon, 17 Jul 2023 14:13:51 +0200 [thread overview]
Message-ID: <87a5vuag74.fsf@48ers.dk> (raw)
In-Reply-To: <8735211cdc.fsf@48ers.dk> (Peter Korsgaard's message of "Thu, 06 Jul 2023 13:57:19 +0200")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
>> Most rpi defconfigs use dtb overlays, but not rpi0 / rpi2 - Making it harder
>> to use overlays on those boards as the genimage files have to be tweaked.
>> To fix this, create the rpi-firmware/overlays directory in the post-build
>> script if needed and unconditionally include it in the genimage files so
>> rpi0/rpi2 works consistently with the other variants.
>> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> Committed, thanks.
Committed to 2023.02.x and 2023.05.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-07-17 12:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 16:46 [Buildroot] [PATCH 1/3] board/raspberry: handle dtb overlays for all variants Peter Korsgaard
2023-07-05 16:46 ` [Buildroot] [PATCH 2/3] board/raspberrypi/post-image.sh: generate genimage config from template if not present Peter Korsgaard
2023-09-29 7:13 ` Peter Korsgaard
2023-07-05 16:46 ` [Buildroot] [PATCH 3/3] board/raspberrypi: drop variant-specific genimage files Peter Korsgaard
2023-07-05 18:10 ` Peter Korsgaard
2023-09-29 7:13 ` Peter Korsgaard
2023-07-06 11:57 ` [Buildroot] [PATCH 1/3] board/raspberry: handle dtb overlays for all variants Peter Korsgaard
2023-07-17 12:13 ` Peter Korsgaard [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=87a5vuag74.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=julien.grossholtz@openest.io \
--cc=martin@barkynet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox