Hi,

> > I further changed the MBR partition type of the first of the three
> > partitions from EFI to FAT16 - starts booting U-Boot, yay!

Could you send the layout of the resulting ptable which you were
able to boot the device with ?

  parted device unit s print

it would help me to do the right fixes in kiwi

> > The bad news is, I don't see how I could tweak either of these in the
> > Kiwi config. :/ It seems that the new partition layout is triggered by
> > firmware="vboot". Does that mean changes need to be done in Kiwi code?

yes. I talked to Alex about this disk layout and I think it's the
best we can do. You are right the vboot firmware caused this layout
and it is used for the Chromebook in the first place. For this device
we needed a real GPT. With raspberry the layout is also a good idea
but we have to use a sync_mbr ptable type. My plan is to configure
this with:

   firmware="vboot" loader="berryboot"

- should create a sync_mbr ptable type
- should create three partitions
  
  1. a fat16 containing u-boot.bin plus config.txt plus cmdline.txt
     plus all the raspberry required firmware stuff. as kernel in
     config.txt we use u-boot.bin which loads boot.scr from the
     second partition

  2. ext2 boot partition, with boot.scr kernel and initrd

  3. root partition

The kiwi script hooks as we use for setting up the different loaders
for the arm boards can be used to change all that. The common parts
which are clear should be done by kiwi though

Thanks

Regards,
Marcus
-- 
 Public Key available
 gpg --keyserver pgp.mit.edu --recv-keys 0xCCE3C6A2
 -------------------------------------------------------
 Marcus Schäfer (Res. & Dev.)   SUSE LINUX Products GmbH
 Tel: 0911-740 53 0             Maxfeldstrasse 5
 FAX: 0911-740 53 479           D-90409 Nürnberg
 GF:  Jeff Hawn,Jennifer Guild, Felix Imendörffer                  
 HRB: 21284 (AG Nürnberg)       Germany
 http://www.suse.de
 -------------------------------------------------------
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to