From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Alexander Shiyan <eagle.alexander923@gmail.com>,
barebox@lists.infradead.org
Subject: Re: [PATCH 1/2] Add support for extlinux.conf
Date: Mon, 27 Apr 2026 10:58:12 +0200 [thread overview]
Message-ID: <ae8lJG6VB2CG-ukg@pengutronix.de> (raw)
In-Reply-To: <29fb6d15-f449-45ee-8b2f-485a618ec573@pengutronix.de>
On Fri, Apr 24, 2026 at 04:53:59PM +0200, Ahmad Fatoum wrote:
> Hello,
>
> On 4/24/26 10:46 AM, Alexander Shiyan wrote:
> >> On 4/16/26 3:45 PM, Alexander Shiyan wrote:
> >>> This adds support for the extlinux.conf configuration format, commonly
> >>> used by Syslinux and many Linux distributions. The configuration file
> >>> is typically located at /boot/extlinux/extlinux.conf or
> >>> /extlinux/extlinux.conf and defines boot entries with kernel, initrd,
> >>> device tree, and command line options.
> > ...
> >>> +static int extlinux_boot(struct bootentry *be, int verbose, int dryrun)
> >>> +{
> >>> + struct extlinux_entry *e =
> >>> + container_of(be, struct extlinux_entry, entry);
> >>> + char *kernel_abs, *initrd_abs = NULL, *fdt_abs = NULL;
> >>> + struct bootm_data data = {};
> >>> + int ret;
> >>> +
> >>> + bootm_data_init_defaults(&data);
> >>> +
> >>> + data.dryrun = max_t(int, dryrun, data.dryrun);
> >>> + data.verbose = max(verbose, data.verbose);
> >>> + data.appendroot = true;
> >>
> >> Not sure this is a good idea because of potential of clashing with
> >> extlinux appended command line options.
> >
> > globalvar_add_bool("extlinux.fix_root", NULL); ?
>
> global.extlinux.strip_root to remove root=
> and bootm.appendroot to add barebox' own root?
We already have the latter, so nothing to do here.
Shouldn't we by default remove the root= option once data->appendroot is
set? Also in the bootspec case we do not want to end up with two root=
options.
Sascha
--
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 |
next prev parent reply other threads:[~2026-04-27 8:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 13:45 Alexander Shiyan
2026-04-16 13:45 ` [PATCH 2/2] Documentation: add extlinux.conf support description Alexander Shiyan
2026-04-22 9:14 ` Ahmad Fatoum
2026-04-24 8:19 ` Alexander Shiyan
2026-04-22 9:10 ` [PATCH 1/2] Add support for extlinux.conf Ahmad Fatoum
2026-04-24 8:46 ` Alexander Shiyan
2026-04-24 14:53 ` Ahmad Fatoum
2026-04-27 8:58 ` Sascha Hauer [this message]
2026-04-27 17:34 ` Alexander Shiyan
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=ae8lJG6VB2CG-ukg@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=eagle.alexander923@gmail.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