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 2/3] board/raspberrypi/post-image.sh: generate genimage config from template if not present
Date: Fri, 29 Sep 2023 09:13:40 +0200 [thread overview]
Message-ID: <87bkdljvtn.fsf@48ers.dk> (raw)
In-Reply-To: <20230705164616.671351-2-peter@korsgaard.com> (Peter Korsgaard's message of "Wed, 5 Jul 2023 18:46:15 +0200")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> The rpi genimage configurations are all identical, except for the boot
> partition files, which include:
> - Device tree files (*.dtb)
> - rpi-firmware files (rpi-firmware/*)
> - Kernel image (Image/zImage)
> All of these are quite simple to figure out programatically based on the
> content of BINARIES_DIR, so extend post-image.sh to fall back to generating
> a genimage configuration based on genimage.cfg.in if a board specific one
> does not exist.
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Committed, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-09-29 7:13 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 [this message]
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
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=87bkdljvtn.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 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.