[coreboot] [PATCH] cross toolchain builder

Carl-Daniel Hailfinger c-d.hailfinger.devel.2006 at gmx.net
Sun Sep 27 00:47:17 CEST 2009

On 26.09.2009 19:38, Stefan Reinauer wrote:
> [...] Just defining coreboot to be this payload free 
> (thus, unusable as is) piece of rom code is also not nice at all.

I'd like to differentiate here.
For working hardware init, the payload and anything after it are almost
completely irrelevant (except for some self-registering option ROMs).
For working boot, the payload and following stuff does matter.

IMHO coreboot is _not_ the full-service singing and dancing firmware
with builtin web browser. It is pure hardware init. Personally, I would
love to split coreboot building and payload integration into completely
separate steps (and thanks to CBFS, we can do that easily). A coreboot
build would always result in a ROM image without payload (after all, the
coreboot configuration and compilation should not depend on the
payload). In an additional step, the payload would be compiled and
integrated into the ROM image.

Example command:
make build_and_insert_payload

OK, maybe not exactly the commands above, but something similar in
style. This is my personal opinion only (because my coreboot recompiles
beat my payload recompiles by a factor of 50) and I can deal with either



More information about the coreboot mailing list