From: Ryan Harper <ryanh@us.ibm.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] BOCHS update with DMI functional
Date: Thu, 14 Feb 2008 12:53:42 -0600 [thread overview]
Message-ID: <20080214185342.GA25080@us.ibm.com> (raw)
I just tested the latest BOCHS from cvs, which includes the DMI/SMBIOS
patch from Filip, with qemu cvs HEAD, and kvm as well and the export DMI
tables are fully functional. Running dmidecide in the guest displays
all of the appropriate information. I was wondering what the process is
for qemu to pull in a new version of BOCHS to include with QEMU. Any
chance of getting the latest BOCHS included so guests can use the new
DMI table generation.
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253 T/L: 678-9253
ryanh@us.ibm.com
next reply other threads:[~2008-02-14 18:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 18:53 Ryan Harper [this message]
2008-02-15 16:33 ` [Qemu-devel] BOCHS update with DMI functional Robert Riebisch
2008-02-15 18:19 ` Ryan Harper
2008-02-16 14:00 ` Robert Riebisch
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=20080214185342.GA25080@us.ibm.com \
--to=ryanh@us.ibm.com \
--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).