Hi Guillaume, Am 23.09.2013 15:47, schrieb Guillaume Gardet:
* Have a proper image for Raspberry Pi : * need kiwi fix (only in git repo ATM) * having u-boot working on RPi (not sure what is the current status) * update images to use u-boot (once u-boot is ok on RPi)
Well, U-Boot has a problem (for me): It's drivers are often very "simple" compared to the linux drivers: * the mmc driver can not read all SSDs. My 16GB Class10 Transcend Cards can not be read by u-boot (they work fine with linux and with bootcode.bin) Other cards (new SanDisk UHS-1 micro-sdhc, and old / cheap no-name cards) work fine. * often, I get "illegal extent" when trying to load the kernel from ext4 after unclean shutdown. But a fsck etc. does not find any problem with the rootfs. The only way to correct this is to create a copy of the kernel and/or initrd, and then rename it to the original filename. => it is not really robust :-( The feature I wanted most from u-boot was the ability to read from ext3/4, read the zImage symlink and maybe having some kind of boot menu. However, I then realized that even though I can display a boot menu, I have no way of doing anything without a serial console, so it is not that much better. So since perl-bootloader/yast need to deal with FAT boot partitions anyway (for UEFI) we can probably just cheat somehow, pretend to be UEFI and just have the FAT partition mounted at /boot. (Hey, I even tried to use the linux kernel as boot loader with a kernel/initrd, "boot menu" script and then load the final kernel and kexec into it, but then kexec failed miserably on the pi m( ) What we could do is use the safe-mode feature to select two different kernels based on the safe-mode GPIO pin or such, but that's all in config.txt, no special magic needed. If you still want to try u-boot on raspi, get home:seife:ARM/u-boot-rpib It contains a patch that gets the original boot args from bootcode.bin env and passes them on to the booted linux kernel. Otherwise some important setup stuff (which seems hardcoded in bootcode.bin and is not in config.txt) will be missing and e.g. the SD card will not work. Best regards, seife -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org