28.10.2015 20:45, Andreas Färber пишет: > Hi Misha, > > Am 28.10.2015 um 17:18 schrieb Misha Komarovskiy: >> On Wed, Oct 28, 2015 at 5:10 PM, Andreas Färber <[email protected]> wrote: >>> 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! >> >> Yes we need to generate this file and put inside resulting JeOS image, >> same way we generate >> boot.scr but to /extlinux folder on boot partition and extlinux.conf >> is not compiled it is plain text file. > > No, strong objection! This is absolutely not like boot.scr but rather > like grub.cfg. It contains entries per kernel, so it needs to be > regenerated on kernel package installation, not just once during JeOS > build time. Therefore my pointing to whatever tools are involved there. > If that gets implemented properly, the JeOS image will automatically get > it through kernel package installation and needs no changes.
I've just looked through perl-bootloader. It is not so hard to implement additional module Extlinux.pm, given there is hardware support to test. But I would say that to implement extlinux support seems to be way easier than direct u-boot anyway. Patching perl-bootloader should be sufficient for correct operation of kernel RPM post/pre scripts. > Also, to really make multi-kernel support work for ARM, we need to fix > the dtb-source package for multiversion support, installing stuff to > /boot/dtb-4.2.3-1 etc. (and update a dtb symlink during %post). That way > you can safely go back to a previously working kernel. Long on my TODO > list to investigate, but hasn't made it to the top yet. Volunteers? You are right here, libzypp also must be aware of dtb package as well as purge-kernels script. > > Regards, > Andreas > -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
