Am 28.10.2015 um 09:31 schrieb Matwey V. Kornilov: > 27.10.2015 22:43, Misha Komarovskiy пишет: >> On Tue, Oct 27, 2015 at 9:52 PM, Matwey V. Kornilov >> <[email protected]> wrote: >>> 27.10.2015 11:04, Guillaume Gardet пишет: >>>> Le 26/10/2015 19:52, Matwey V. Kornilov a écrit : >>>>> Why bootmenu command is not used atm? Are there any reasons? >> >> You mean ansi bootmenu? If yes, ac100 community member tried to enable >> it for our board, >> but extlinux.conf was proposed as better solution, here is link >> http://patchwork.ozlabs.org/patch/450122/ >> >> I tried to use extlinux.conf with openSUSE on Chromebook Snow, >> because its support already enabled there, and it work flawlessly and >> very flexible, >> take a look at README.distro in u-boot repo, also as it is same as pxe >> config file kiwi probably already have >> support for it. >> >> Here is example of my test extlinux.conf: [...] > Nice. I cannot understand is it uboot who runs extlinux or just support > of extlinux configuration file syntax inside uboot?
As far as I understand, someone would need to generate such config file into the filesystem for U-Boot to read. That's the big problem I see with it. If you want to dive into YaST, perl-bootloader or whatever is involved there, feel free to give it a try! Some solution for handling multiple kernels is bitterly needed. In YaST not even grub2 was supported on ARMv7 last time I tried - that's the alternative to extlinux. It requires CONFIG_API to be enabled, for which I have a u-boot branch. It also requires grub2 to be patched for the RAM address of some boards. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
