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@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
