From: "Rafał Miłecki" <zajec5@gmail.com>
To: buildroot@buildroot.org
Cc: "Rafał Miłecki" <rafal@milecki.pl>
Subject: [Buildroot] [PATCH] board/broadcom/northstar: fix building custom images
Date: Wed, 3 Jan 2024 07:32:53 +0100 [thread overview]
Message-ID: <20240103063253.6833-1-zajec5@gmail.com> (raw)
From: Rafał Miłecki <rafal@milecki.pl>
Custom Northstar images allow installing (flashing) them using vendor UI
or CFE bootloader. Change of DTS files paths ("broadcom/" prefix
introduction) prevented post script from generating them.
Adjust post-image.sh to deal with new paths.
Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
---
board/broadcom/northstar/post-image.sh | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/board/broadcom/northstar/post-image.sh b/board/broadcom/northstar/post-image.sh
index b6150fc539..559ed8bf4b 100755
--- a/board/broadcom/northstar/post-image.sh
+++ b/board/broadcom/northstar/post-image.sh
@@ -27,8 +27,9 @@ build_trx() {
rm -f $images/zImage.$device.lzma
}
-devices="$(sed -n 's/^BR2_LINUX_KERNEL_INTREE_DTS_NAME="\([a-z0-9 \-]*\)"$/\1/p' ${BR2_CONFIG})"
+devices="$(sed -n 's/^BR2_LINUX_KERNEL_INTREE_DTS_NAME="\([^"]*\)"$/\1/p' ${BR2_CONFIG})"
for device in $devices; do
+ device="${device#broadcom/}"
case "$device" in
"bcm4708-smartrg-sr400ac")
build_trx "$1" "$device"
--
2.35.3
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2024-01-03 6:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 6:32 Rafał Miłecki [this message]
2024-01-13 21:04 ` [Buildroot] [PATCH] board/broadcom/northstar: fix building custom images 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=20240103063253.6833-1-zajec5@gmail.com \
--to=zajec5@gmail.com \
--cc=buildroot@buildroot.org \
--cc=rafal@milecki.pl \
/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