On 25.01.2013, at 14:53, Guillaume Gardet wrote:
Le 25/01/2013 14:45, Alexander Graf a écrit :
> On 25.01.2013, at 14:41, Guillaume Gardet wrote:
>> Le 25/01/2013 14:34, Alexander Graf a écrit :
>>> On 25.01.2013, at 14:30, Guillaume Gardet wrote:
>>>> Finaly, I got an image from OBS for Raspberry Pi (armv5 image) but I have
the following problem.
>>>> All boot files (kernel image, etc.) are in /boot folder from ext3
partition, not in FAT32 boot partition.
>>>> Any idea why? So that we could fix it?
>>> Do you really need the /boot folder to be vfat? Couldn't you live with a
FAT jump partition that contains u-boot and then boots the kernel from an ext3 /boot?
>>> That's how we boot the chromebook, and it makes life a lot easier.
>> Raspberry Pi must have a FAT partition with a binary bootloader which init the
board and loads directly the kernel image. So, FAT boot partition is mandatory... :(
>> RPi has lots of proprietary/closed soft which does not help to hack.
> Sure, but that does not mean that /boot needs to be on FAT, right?
Not sure I understand what you mean.
Rom bootloader loads closed binary bootloader from FAT partition to RAM and then this
bootloader is looking for kernel image on the FAT partition, so we need to have it their.
Nonono. The Rom bootloader loads the closed source binary loader from a FAT
partition. This bootloader looks for a binary to execute from a FAT partition.
That binary could just as well be https://github.com/gonzoua/u-boot-pi/tree/rpi
That u-boot could then read a boot.scr from an ext3 partition and load the kernel+initrd
from an ext3 partition.
Hence, /boot can be ext3. You need a jump partition with
* closed source binary bootloader
Ok, so we should add another boot stage with u-boot. Ok, I understand what you want to
Will kiwi install u-boot in the FAT partition?
Is there some value added with u-boot except this workaround? Otherwise, we will get a
longer boot time for "nothing".