From: Sascha Hauer <s.hauer@pengutronix.de>
To: Christian Eggers <ceggers@arri.de>
Cc: barebox@lists.infradead.org, ceggers@gmx.de
Subject: Re: [RFC PATCH] bootm: Register as bootentry provider
Date: Mon, 27 Jan 2020 13:49:38 +0100 [thread overview]
Message-ID: <20200127124938.ajhbdy2rev7ijz2c@pengutronix.de> (raw)
In-Reply-To: <20200127101831.27601-1-ceggers@arri.de>
On Mon, Jan 27, 2020 at 11:18:31AM +0100, Christian Eggers wrote:
> > Obviously anything involving shell scripts cannot work when no shell is
> > enabled. I suggest using bootloader spec (CONFIG_BLSPEC) to boot a
> > kernel. This works without shell support.
>
> I would like to avoid using bootloader spec. The patch below works fine
> for me. Do you think that this (or something similar) can be added to
> barebox?
>
>
> Support for "boot <device>". This is required for using bootchooser with
> CONFIG_SHELL_NONE. In this case no boot scripts can be used, so the
> device name of the flash partition containing the kernel image has to
> provided.
>
> Only enabled if CONFIG_BLSPEC is disabled.
>
> Example: bootchooser.system0.boot=nand0.root.ubi.kernel0
you could leave bootchooser.system0.boot empty in which case bootchooser
tries to boot something called "system0".
Like in your patch below call bootentry_register_provider() from your
boardcode and put behind "system0" whatever you want.
I don't like interpreting a device name as a kernel image very much,
given that there's no possibility to also specify the devicetree and
commandline.
Another thing is that just enabling CONFIG_BLSPEC in a config shouldn't
prevent a board from booting. the "Only enabled if CONFIG_BLSPEC is
disabled" is not an option here.
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 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2020-01-27 12:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 16:38 Configuring for secure boot Christian Eggers
2020-01-20 19:53 ` Sascha Hauer
2020-01-21 10:52 ` Ahmad Fatoum
2020-01-21 11:11 ` Sascha Hauer
2020-01-23 10:29 ` Configuring for secure boot / Using bootchooser Christian Eggers
2020-01-27 10:07 ` Sascha Hauer
2020-01-27 10:18 ` [RFC PATCH] bootm: Register as bootentry provider Christian Eggers
2020-01-27 12:49 ` Sascha Hauer [this message]
2020-01-27 19:26 ` Christian Eggers
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=20200127124938.ajhbdy2rev7ijz2c@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=ceggers@arri.de \
--cc=ceggers@gmx.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