2008/7/22, Kevin O'Connor kevin@koconnor.net:
Hi,
Several people have raised the possibility of replacing the coreboot BIOS emulation for option roms with SeaBIOS.
[...]
So, I can see a mode where coreboot would lzma uncompress a minimal seabios into 0xf0000, call into seabios, seabios would then init itself and return to coreboot. Then coreboot would finish initialization and launch the payload from flash.
I can see where the above would be useful if the payload is always coming out of flash. However, if the user ever needs to boot using seabios (or via a scsi/pxe option rom) then I think seabios needs to be the payload and needs to drive the bootup.
so if I want to write the int13 for scsi booting, should I write interrupt function in coreboot and inject it to int13, or just write codes in seabios?
If there is interest in doing this, we'll need to figure out how to work out the interactions. Zhang Rui is currently working on having seabios return to coreboot. As for code integration - I'd like to avoid forking the seabios code. Perhaps it would be okay to simply copy a seabios binary into the svn repo with directions on how to build it manually. (This is what qemu and bochs do for their bios blobs.)
Maybe this is the simplest way.