On Sun, Sep 11, 2011 at 3:53 PM, tiho taskov tihokibertron@gmail.comwrote:
I want to know what stance the coreboot community is taking on the issue with identifying basic initialization parameters for a pre-compiled linux kernel booting on a random SoC.
From Coreboot's perspective, this sort of thing should be handled in the
payload / bootloader (SeaBIOS, GRUB/GRUB2, etc).
FWIW, there have also been discussions about using U-Boot as a payload for Coreboot: http://blogs.coreboot.org/blog/2011/04/30/u-boot-as-coreboot-payload/ . One advantage of the U-Boot approach is that U-Boot supports the Flattened Device Tree (FDT) which is useful for passing init parameters, device topology, etc. to Linux. AFAIK, this is the standard approach for PowerPC, is gaining popularity for ARM, and can also be applied to x86. Here are some additional resources if this interests you: 2011 Linux Plumbers Conference talk: http://linuxplumbersconf.org/ocw/proposals/47 2010 Embedded Linux Conference talk: http://elinux.org/images/b/b6/ARM_Device_Tree_Status_Report.pdf