From: Gleb Natapov <gleb@redhat.com>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: qemu-devel@nongnu.org, Sebastian Herbszt <herbszt@gmx.de>
Subject: [Qemu-devel] Re: [PATCH][SEABIOS] Make SMBIOS table pass MS SVVP test
Date: Tue, 24 Nov 2009 20:41:47 +0200 [thread overview]
Message-ID: <20091124184147.GA22992@redhat.com> (raw)
In-Reply-To: <20091124175300.GD17606@morn.localdomain>
On Tue, Nov 24, 2009 at 12:53:00PM -0500, Kevin O'Connor wrote:
> On Tue, Nov 24, 2009 at 06:59:01PM +0200, Gleb Natapov wrote:
> > On Tue, Nov 24, 2009 at 10:57:02AM -0500, Kevin O'Connor wrote:
> > > On Mon, Nov 23, 2009 at 08:30:41PM +0200, Gleb Natapov wrote:
> > > > On Mon, Nov 23, 2009 at 07:15:55PM +0100, Sebastian Herbszt wrote:
> > > > > Ok - sounds good if bios_characteristics gets proper system based values.
> > > > >
> > > > Kevin can you help here. I can send a patch, but I am not sure I know
> > > > everything SeaBIOS supports.
> > >
> > > I don't know what bios_characteristics should be set to.
> > >
> > http://www.phoenix.com/NR/rdonlyres/51EEA1E6-20C1-4FA2-A3D8-AD8E45335C47/0/specssmbios.pdf
> > Page 30 have the description.
>
> Bit 4 ISA is supported
> Bit 7 PCI is supported
> Bit 9 Plug and Play is supported
> Bit 10 APM is supported
> Bit 12 BIOS shadowing is allowed
> Bit 15 Boot from CD is supported
> Bit 16 Selectable Boot is supported
> Bit 19 EDD (Enhanced Disk Drive) Specification is supported
> Bit 22 Int 13h - 5.25" / 360 KB Floppy Services are supported
> Bit 23 Int 13h - 5.25" /1.2MB Floppy Services are supported
> Bit 24 Int 13h - 3.5" / 720 KB Floppy Services are supported
> Bit 25 Int 13h - 3.5" / 2.88 MB Floppy Services are supported
> Bit 27 Int 9h, 8042 Keyboard services are supported
> Bit 28 Int 14h, Serial Services are supported
> Bit 29 Int 17h, Printer Services are supported
> Bit 30 Int 10h, CGA/Mono Video Services are supported
>
> Several of the above are dependent on CONFIG_xxx settings.
>
> However, I'm not really sure how the above overlaps with your SVVP
> patch..
>
It is not. I am just thinking about putting real info there instead of
"not supported". SVVP pass as it is. Do you prefer to leave it as is?
--
Gleb.
next prev parent reply other threads:[~2009-11-24 18:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-22 14:08 [Qemu-devel] [PATCH][SEABIOS] Make SMBIOS table pass MS SVVP test Gleb Natapov
2009-11-22 16:51 ` [Qemu-devel] " Sebastian Herbszt
2009-11-22 17:21 ` Gleb Natapov
2009-11-22 17:39 ` Sebastian Herbszt
2009-11-22 19:51 ` Gleb Natapov
2009-11-22 20:41 ` Sebastian Herbszt
2009-11-23 7:28 ` Gleb Natapov
2009-11-23 18:15 ` Sebastian Herbszt
2009-11-23 18:30 ` Gleb Natapov
2009-11-23 18:48 ` Sebastian Herbszt
2009-11-23 19:39 ` Gleb Natapov
2009-11-24 8:18 ` Gleb Natapov
2009-11-24 15:57 ` Kevin O'Connor
2009-11-24 16:59 ` Gleb Natapov
2009-11-24 17:53 ` Kevin O'Connor
2009-11-24 18:41 ` Gleb Natapov [this message]
2009-11-24 20:30 ` Kevin O'Connor
2009-11-25 20:09 ` Sebastian Herbszt
2009-11-26 7:39 ` Gleb Natapov
2009-11-26 21:38 ` Sebastian Herbszt
2009-11-22 19:58 ` Yaniv Kaul
2009-11-22 23:57 ` Carl-Daniel Hailfinger
2009-11-23 6:28 ` Gleb Natapov
2009-11-23 18:02 ` Sebastian Herbszt
2009-11-23 11:56 ` Gleb Natapov
2009-11-22 17:07 ` Kevin O'Connor
2009-11-23 11:08 ` Gleb Natapov
2009-11-24 14:40 ` Kevin O'Connor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091124184147.GA22992@redhat.com \
--to=gleb@redhat.com \
--cc=herbszt@gmx.de \
--cc=kevin@koconnor.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).