[coreboot] Group demographics

[Julius Werner]

>
> As fallback/payload is compressed in bios.bin, I'm not sure what strings
> will provide.
> I did run strings on bios.bin (as well as looking at it in hex editor) and
> found nothing
> explicitly suggesting depthcharge (or u-boot for that matter) was the
> payload.  I made
> assumption u-boot was payload based on presence of u-boot.dtb file in
> bios.bin.
>

u-boot.dtb is an ancient leftover that we haven't bothered to remove yet
(or, rather, I think it might actually be gone from the latest boards...
try a Kevin image). IIRC it actually contains the coreboot config or
something weird? Anyway, red herring.


> I welcome pointers to online documentation (either coreboot or chromiumos)
> that more clearly discuss coreboot inclusion within chromiumos build and
> development cycle.
>

Not much documentation unfortunately, in part because it keeps changing too
often to be worth documenting. Your best bet is to just look at the ebuild
sources directly:

https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/master/sys-boot/coreboot/coreboot-9999.ebuild
https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/master/sys-boot/libpayload/libpayload-9999.ebuild
https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/master/sys-boot/depthcharge/depthcharge-9999.ebuild
https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/master/sys-boot/chromeos-bootimage/chromeos-bootimage-9999.ebuild

Hope you like portage, because that's all we have! ;)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20170328/b97640d6/attachment.html>