From: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"Kiszka, Jan" <jan.kiszka@siemens.com>
Cc: "Bezdeka, Florian" <florian.bezdeka@siemens.com>
Subject: Re: [PATCH 2/4] refactor loading of DT overlays in uboot
Date: Thu, 31 Aug 2023 04:56:20 +0000 [thread overview]
Message-ID: <32eaef64ffe1380d142822d2d0e9ac1256ae4900.camel@siemens.com> (raw)
In-Reply-To: <4bf2da43-5ff6-4950-09df-737900c441ec@siemens.com>
On Tue, 2023-08-08 at 10:48 +0200, Jan Kiszka wrote:
> On 01.08.23 11:37, Felix Moessbauer wrote:
> > As we already expand the DT overlays variable in the code
> > generation, we
> > do not need to loop over the elements in the generated code again.
> > This
> > reduces the size of the boot.src script a little and makes it
> > better
> > readable.
> >
> > No functional change.
> >
> > Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> > ---
> > meta/recipes-bsp/u-boot-script/files/update-u-boot-script | 6 ++--
> > --
> > 1 file changed, 2 insertions(+), 4 deletions(-)
> >
> > diff --git a/meta/recipes-bsp/u-boot-script/files/update-u-boot-
> > script b/meta/recipes-bsp/u-boot-script/files/update-u-boot-script
> > index e9ace15e..14a81563 100755
> > --- a/meta/recipes-bsp/u-boot-script/files/update-u-boot-script
> > +++ b/meta/recipes-bsp/u-boot-script/files/update-u-boot-script
> > @@ -63,13 +63,11 @@ if [ -n "${OVERLAYS}" ]; then
> > if ! echo $OVERLAY | grep -q "^/"; then
> > OVERLAY_PATH=/usr/lib/linux-image-
> > ${KERNEL_VERSION}/
> > fi
> > - echo "for entry in ${OVERLAY}; do" >> ${BOOT_CMD}
> > - echo "echo Loading ${OVERLAY_PATH}\${entry}..." >>
> > ${BOOT_CMD}
> > + echo "echo Loading ${OVERLAY_PATH}${OVERLAY} ..."
> > >> ${BOOT_CMD}
> > echo "load \${devtype}
> > \${devnum}:${ROOT_PARTITION}" \
> > - "\${overlay_addr_r} ${OVERLAY_PATH}\${entry}"
> > \
> > + "\${overlay_addr_r} ${OVERLAY_PATH}${OVERLAY}"
> > \
> > >> ${BOOT_CMD}
> > echo "fdt apply \${overlay_addr_r}" >> ${BOOT_CMD}
> > - echo "done" >> ${BOOT_CMD}
> > done
> > fi
> >
>
> NACK, see commit 8b9f930410234ad46135df3642bc0c7053fc854b.
Ok, got it. But there should be a comment in the code about this
particular detail. I'll add one when re-proposing the u-boot DT patches
which unfortunately got reverted as well.
Felix
>
> Jan
>
next prev parent reply other threads:[~2023-08-31 4:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 9:37 [PATCH 0/4] Rework and extend u-boot-script for DT overlays Felix Moessbauer
2023-08-01 9:37 ` [PATCH 1/4] fix(u-boot-script): use correct ramdisk size Felix Moessbauer
2023-08-03 10:22 ` Gylstorff Quirin
2023-08-01 9:37 ` [PATCH 2/4] refactor loading of DT overlays in uboot Felix Moessbauer
2023-08-08 8:48 ` Jan Kiszka
2023-08-31 4:56 ` MOESSBAUER, Felix [this message]
2023-08-01 9:37 ` [PATCH 3/4] u-boot-script: add support to use builtin dt Felix Moessbauer
2023-08-01 9:37 ` [PATCH 4/4] use builtin DT for nanopi-neo target Felix Moessbauer
2023-08-08 8:48 ` Jan Kiszka
2023-08-31 5:34 ` MOESSBAUER, Felix
2023-08-31 7:01 ` Jan Kiszka
2023-08-31 7:07 ` MOESSBAUER, Felix
2023-08-08 7:05 ` [PATCH 0/4] Rework and extend u-boot-script for DT overlays Uladzimir Bely
2023-08-08 10:24 ` Jan Kiszka
2023-08-09 5:40 ` Uladzimir Bely
2023-08-09 7:43 ` Baurzhan Ismagulov
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=32eaef64ffe1380d142822d2d0e9ac1256ae4900.camel@siemens.com \
--to=felix.moessbauer@siemens.com \
--cc=florian.bezdeka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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