On Tue, 2011-05-24 at 22:44 -0400, Kevin O'Connor wrote:
> On Tue, May 24, 2011 at 12:02:07PM +0100, Ian Campbell wrote:
> > Would that involve pulling a bunch of mainboard specific stuff from
> > coreboot into SeaBIOS?
>
> The idea - when it was last raised - was to provide raw info in a
> coreboot specific manor (via the "coreboot tables"), and then have
> SeaBIOS populate ACPI/SMBIOS/MPTable/etc. from that info. It was
> never pursued.
Speaking of coreboot tables... I also need to pass some start of day
info into seabios (ACPI tables, e820 etc). Currently I just used a
little ad-hoc data structure at a known physical address but I wonder if
perhaps I should/could reuse the coreboot table datastructures? They are
existing and well defined and I suppose they are pretty static, but I
don't want to add any additional compatibility burden if you guys would
rather avoid it.
FWIW my current patch for hvmloader->seabios (rather than direct SeaBIOS
boot) is attached. Things I'd like to address before submitting it
properly are putting the hypercall pages somewhere saner (and reserved
etc) and using coreboot tables if desired (or at the very least do
something better than commenting out the "static"...). I also attached
the patches for hvmloader.
Ian.
0001-Add-basic-support-for-use-as-Xen-HVM-BIOS.patch
Description: Text Data
xen-hvmloader-per-bios-roms.patch
Description: Text Data
xen-further-seabios-support.patch
Description: Text Data
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|