mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Jonas Rebmann <jre@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH] Debug: add Kconfig option to abort autoboot
Date: Wed, 25 Feb 2026 10:52:39 +0100	[thread overview]
Message-ID: <b78fe423-6e5e-4173-b24e-c69f120479a1@pengutronix.de> (raw)
In-Reply-To: <aZ6qrxsMDv9FU-P2@pengutronix.de>

On 2026-02-25 08:54, Sascha Hauer wrote:
> On Tue, Feb 24, 2026 at 04:59:00PM +0100, Jonas Rebmann wrote:
>> Hi Sascha,
>>
>> On 2026-02-23 16:39, Sascha Hauer wrote:
>>> For debugging purposes it's sometimes useful when barebox doesn't boot
>>> through, but stops at the prompt.
>>
>> Isn't this already compile-time configurable by setting the defaultenv
>> autoboot to "abort"?
> 
> Yes, it is. It's just easier sometimes to just change a config, at least
> for Claude.

I think for the human, managing one option in two systems in different
ways makes things confusing. If the change is really needed, I suggest
the help text could explain that this overrides global.autoboot and that
configuration via defaultenv has further options for boot behavior.
Maybe also the autoboot global help text could be extended: "Autoboot
state. Possible values: countdown (default), abort, halt, menu, boot.
Ineffective if overwritten by CONFIG_DEBUG_AUTOBOOT_ABORT."

Regards,
Jonas

-- 
Pengutronix e.K.                           | Jonas Rebmann               |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-9    |



  reply	other threads:[~2026-02-25  9:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-23 15:39 Sascha Hauer
2026-02-24 15:59 ` Jonas Rebmann
2026-02-25  7:54   ` Sascha Hauer
2026-02-25  9:52     ` Jonas Rebmann [this message]
2026-02-25 10:11       ` 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=b78fe423-6e5e-4173-b24e-c69f120479a1@pengutronix.de \
    --to=jre@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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