Hi, > I guess -bios would load coreboot. Coreboot would siphon the data > necessary for ACPI table building through the current (same) fw_cfg > bottleneck, build the tables,
Yes. > load the boot firmware (SeaBIOS or OVMF or > something else -- not sure how to configure that), The coreboot rom has named sections (this is called cbfs which stands for coreboot filesystem IIRC): rincewind kraxel ~# cbfstool /usr/share/coreboot.git/bios.bin print bios.bin: 256 kB, bootblocksize 848, romsize 262144, offset 0x0 alignment: 64 bytes Name Offset Type Size cmos_layout.bin 0x0 cmos_layout 1160 fallback/romstage 0x4c0 stage 14419 fallback/coreboot_ram 0x3d80 stage 37333 config 0xcfc0 raw 2493 fallback/payload 0xd9c0 payload 56969 vgabios/sgabios 0x1b8c0 raw 4096 (empty) 0x1c900 null 144216 where "fallback/payload" is seabios. > and pass down the > tables to the firmware (through a now unspecified interface -- perhaps > the tables could even be installed at this point). As far I know coreboot can add more stuff such as acpi tables to cbfs at runtime and seabios able to access cbfs too and pull informations from coreboot that way. HTH, Gerd _______________________________________________ SeaBIOS mailing list SeaBIOS@seabios.org http://www.seabios.org/mailman/listinfo/seabios