Hi Sascha, Am Montag, 27. Januar 2020, 13:49:38 CET schrieb Sascha Hauer: > 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? > > > > > 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. works fine, thanks. > 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. Agreed. > > Sascha regards Christian _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
