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:
Hi,
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. I thought what was done with OMAP at the beginning was a FAT boot partition which was mounted on /boot folder from ext3 partition. Guillaume
Alex
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org