qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] Re: [PATCH][SEABIOS] Move qemu config port access functions


From: Kevin O'Connor
Subject: [Qemu-devel] Re: [PATCH][SEABIOS] Move qemu config port access functions into separate file.
Date: Sat, 19 Sep 2009 11:16:41 -0400
User-agent: Mutt/1.5.19 (2009-01-05)

On Fri, Sep 18, 2009 at 01:01:20PM +0300, Gleb Natapov wrote:
> On Thu, Sep 17, 2009 at 09:24:11PM -0400, Kevin O'Connor wrote:
> > On coreboot there is the Coreboot FileSystem (CBFS).  Basically, the
> > flash stores a series of named files, and SeaBIOS knows how to iterate
> > through them.  So, for instance, one might find the file
> > "pci1013,00b8.rom" which contains an option rom for pci device
> > 1013:00b8, or one might find "floppyimg/FreeDOS" with an image of a
> > floppy to be emulated.
> > 
> > So, ideally qemu would do something similar.  Maybe something like:
> Qemu already does something different. For instance acpi tables are
> transfered as stream formated like this:
> <table count><1 table length><table data><2 table length><table data>
> ...<n table length><table data>

Maybe a stream could be introduced with something like:
<name><len><data> <name2><len2><data2> ...

> I don't think qemu should expose file system API to a BIOS.

To be clear, I'm not proposing exposing the system's filesystem to the
guest.

It's really just a way of getting name=value pairs.  If there is a
different way to do this then that's fine.  Ideally, to fit with
SeaBIOS' current code, there would be a way to obtain the size and
data for a given "name" along with an ability to iterate through the
list of "names" available.

-Kevin




reply via email to

[Prev in Thread] Current Thread [Next in Thread]