On Wed, Mar 26, 2014 at 06:36:10PM -0400, Kevin O'Connor wrote: > On Wed, Mar 26, 2014 at 03:58:50PM -0400, Gabriel L. Somlo wrote: > > - SeaBIOS is still in charge of providing the smbios_entry_point > > structure, and it's unlikely we can reasonably expect it to > > bump the version to 2.5 (not that it seems to matter, if my > > tests are to be believed) > > This is why ultimately we want to use the romfile_loader mechanism for > smbios - that interface will allow qemu to generate both the smbios > table and the smbios entry point.
Ah, so romfile_loader is the "whole-blob" fw_cfg transfer method (so far in smbios.c we've been dealing with individual fields, and individual table types). The only sticking point remaining would be who gets to generate the Type 0 (BIOS Information) table and when, which is something QEMU should arguably NOT be doing on behalf of SeaBIOS (or OVMF, or ...). I guess everyone's busy with QEMU 2.0, so I'll keep playing with this stuff on my own and bring it up again afterwards. Obviously, more comments and feedback are welcome at any time, should there be any interest :) Thanks, --Gabriel
