Not quite yet. I just hopped on a plane this evening and am in San Francisco for the ARM Tech Con next week. I do have the AC100 so I will try to finish unbreaking the initramfs support in that Chrome kernel and getting it to LVM boot properly with the internal flash (the internal flash has 14 partitions that are always recreated by the built-in bootloader if you try to change them, therefore the obvious and easy answer is to use PVs backed onto those...which works - and actually I found a discard problem there with ext4 creation - but the initramfs code in that 2.6.38 kernel folks are using has been messed around with somehow). I haven't looked yet beyond realizing it will refuse to boot properly if given a valid initramfs image and will ignore the root setup you tell it to use.
Anyway...long story short, I'll have something up soon.
Creating a Fedora ARM distribution part 2: Bootstrapping
Posted Oct 22, 2011 11:13 UTC (Sat) by juliank (subscriber, #45896)
[Link]
Be sure to not have other problems. For example, klibc stuff does not work completely on Tegra 2 hardware, thus causing init to die and the boot to fail; unless you patched it of course.
Creating a Fedora ARM distribution part 2: Bootstrapping
Posted Oct 22, 2011 11:14 UTC (Sat) by juliank (subscriber, #45896)
[Link]
That is, if you use klibc things for init. I don't know Fedora's initramfs.
Creating a Fedora ARM distribution part 2: Bootstrapping
Posted Oct 23, 2011 6:20 UTC (Sun) by jcm (subscriber, #18262)
[Link]
Thanks for the comments. In this case everyone with an AC100 is using a nonstandard kernel still so the problem is actually that that kernel is intended for the various Google OSes and not LVM backed root on MTD :) It ought to work but will take some hotel room poking next week.