From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PATCH 0/2] q35: two little patches
Date: Tue, 8 Jan 2013 10:31:05 +0100 [thread overview]
Message-ID: <1357637467-13674-1-git-send-email-kraxel@redhat.com> (raw)
Hi,
Patch 1 adds a intel HD Audio controller with the ich9 PCI IDs
(otherwise identical to the existing ich6 one).
Patch 2 documents the q35 chipset devices.
cheers,
Gerd
Gerd Hoffmann (2):
q35: add ich9 intel hda controller
q35: document chipset devices
docs/q35-chipset.cfg | 129 ++++++++++++++++++++++++++++++++++++++++++++++++++
hw/intel-hda.c | 41 +++++++++++++---
2 files changed, 163 insertions(+), 7 deletions(-)
create mode 100644 docs/q35-chipset.cfg
next reply other threads:[~2013-01-08 9:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 9:31 Gerd Hoffmann [this message]
2013-01-08 9:31 ` [Qemu-devel] [PATCH 1/2] q35: add ich9 intel hda controller Gerd Hoffmann
2013-01-08 9:31 ` [Qemu-devel] [PATCH 2/2] q35: document chipset devices Gerd Hoffmann
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=1357637467-13674-1-git-send-email-kraxel@redhat.com \
--to=kraxel@redhat.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).