mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Alexander Shiyan <eagle.alexander923@gmail.com>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v2 1/2] Add support for extlinux.conf
Date: Tue, 5 May 2026 16:01:37 +0300	[thread overview]
Message-ID: <CAP1tNvTccMsDKF4GVq+z-cDzeaLs3A6s0h-Mrfre8hph8y90fQ@mail.gmail.com> (raw)
In-Reply-To: <76f2bbf8-e069-4cbc-8f14-f473ed731c0f@pengutronix.de>

There is another question: is it necessary to call
globalvar_remove("linux.bootargs.dyn.bootentries")
in extlinux_entry_free()?
We can run bootm multiple times in dry-run mode, and the variable may
become invalid...

вт, 5 мая 2026 г. в 15:52, Ahmad Fatoum <a.fatoum@pengutronix.de>:
>
> Hi,
>
> On 5/5/26 2:44 PM, Alexander Shiyan wrote:
> > barebox@Diasom DS-RK3568-SOM-EVB:/ global
>
> > Loading ARM aarch64 Linux/EFI image '/mnt/mmc1.2/boot/extlinux/../vmlinuz'
> > Camera IMX662 detected.
> > commandline: console=ttyS2,1500000n8 root=LABEL=ROOT ro
> > systemd.unit=setup.target quiet splash  root=/dev/mmcblk1p3
> > systemd.machine_id=181af2816b4c6b0aef77068e0ccc69ad
> > Loaded kernel to 0x0a400000, devicetree at 0x000000000fb49000
> > nv variables modified, saving them
> > I/TC: Secondary CPU 1 initializing
> > I/TC: Secondary CPU 1 switching to normal world boot
> > I/TC: Secondary CPU 2 initializing
> > I/TC: Secondary CPU 2 switching to normal world boot
> > I/TC: Secondary CPU 3 initializing
> > I/TC: Secondary CPU 3 switching to normal world boot
> >
> > Now it works!
>
> Great. I think with the rest of my feedback integrated, the v3 should be
> good to go.
>
> Thanks,
> Ahmad
>
> >
> > вт, 5 мая 2026 г. в 15:22, Ahmad Fatoum <a.fatoum@pengutronix.de>:
> >>
> >> Hello Alexander,
> >>
> >> On 5/5/26 2:19 PM, Alexander Shiyan wrote:
> >>> barebox@Diasom DS-RK3568-SOM-EVB:/ global
> >>> * bootm.~appendroot: true
> >>
> >> This should be bootm.appendroot: 1.
> >>
> >>> bootm.~appendroot: true, but now is ever not added to the cmdline.
> >>
> >> The tilde is just an implementation detail in common/bootm.c. You should
> >> just global.bootm.appendroot as before.
> >>
> >> Thanks,
> >> Ahmad
> >>
> >>>
> >>> вт, 5 мая 2026 г. в 13:49, Ahmad Fatoum <a.fatoum@pengutronix.de>:
> >>>>
> >>>> Hello Alexander,
> >>>>
> >>>> On 5/5/26 12:47 PM, Alexander Shiyan wrote:
> >>>>> Hello Ahmad.
> >>>>>
> >>>>> ...
> >>>>>>> +     if (e->append) {
> >>>>>>> +             char *append;
> >>>>>>> +
> >>>>>>> +             /*
> >>>>>>> +              * The same rootfs image may be launched from eMMC or SD card.
> >>>>>>> +              * Remove any hardcoded root= parameter from "append" to avoid
> >>>>>>> +              * conflicts, then let barebox automatically add the correct
> >>>>>>> +              * root= (via global.bootm.appendroot) based on the boot device.
> >>>>>>> +              */
> >>>>>>> +             if (data.appendroot)
> >>>>>>> +                     append = remove_param(e->append, "ROOT=");
> >>>>> ...
> >>>>>> I thus have a question to you: What happens if you drop remove_param()
> >>>>>> completely? Sure we will have two root=, but the later gets precedence,
> >>>>>> so your use case would continue to work without giving users a wrong
> >>>>>> expectation.
> >>>>>
> >>>>> Yes, the second one takes priority.
> >>>>> The second one is the one added via extlinux.conf APPEND option.
> >>>>> In our case we need the first parameter, i.e. which comes from barebox
> >>>>> when global.bootm.appendroot is toggled on.
> >>>>
> >>>> Ack. Please check the series I Cc'd you on, which ensures that
> >>>> global.bootm.appendroot applies _after_ extlinux.conf APPEND.
> >>>>
> >>>> Thanks,
> >>>> Ahmad
> >>>>
> >>>>>
> >>>>> Thanks!
> >>>>>
> >>>>
> >>>> --
> >>>> Pengutronix e.K.                  |                             |
> >>>> Steuerwalder Str. 21              | http://www.pengutronix.de/  |
> >>>> 31137 Hildesheim, Germany         | Phone: +49-5121-206917-0    |
> >>>> Amtsgericht Hildesheim, HRA 2686  | Fax:   +49-5121-206917-5555 |
> >>>>
> >>>
> >>
> >> --
> >> Pengutronix e.K.                  |                             |
> >> Steuerwalder Str. 21              | http://www.pengutronix.de/  |
> >> 31137 Hildesheim, Germany         | Phone: +49-5121-206917-0    |
> >> Amtsgericht Hildesheim, HRA 2686  | Fax:   +49-5121-206917-5555 |
> >>
> >
>
> --
> Pengutronix e.K.                  |                             |
> Steuerwalder Str. 21              | http://www.pengutronix.de/  |
> 31137 Hildesheim, Germany         | Phone: +49-5121-206917-0    |
> Amtsgericht Hildesheim, HRA 2686  | Fax:   +49-5121-206917-5555 |
>



  reply	other threads:[~2026-05-05 13:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-28 13:28 Alexander Shiyan
2026-04-28 13:28 ` [PATCH v2 2/2] Documentation: add extlinux.conf support description Alexander Shiyan
2026-05-05  9:56 ` [PATCH v2 1/2] Add support for extlinux.conf Ahmad Fatoum
2026-05-05 10:47   ` Alexander Shiyan
2026-05-05 10:49     ` Ahmad Fatoum
2026-05-05 12:19       ` Alexander Shiyan
2026-05-05 12:22         ` Ahmad Fatoum
2026-05-05 12:44           ` Alexander Shiyan
2026-05-05 12:52             ` Ahmad Fatoum
2026-05-05 13:01               ` Alexander Shiyan [this message]
2026-05-05 13:04                 ` Ahmad Fatoum

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=CAP1tNvTccMsDKF4GVq+z-cDzeaLs3A6s0h-Mrfre8hph8y90fQ@mail.gmail.com \
    --to=eagle.alexander923@gmail.com \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    /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