From: "Michael S. Tsirkin" <mst@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
kvm-devel <kvm@vger.kernel.org>,
Juan Quintela <quintela@redhat.com>
Subject: [Qemu-devel] [PATCHv5-repost 0/2] qemu: cirrus reset-related fixes
Date: Mon, 30 Nov 2009 21:02:19 +0200 [thread overview]
Message-ID: <20091130190219.GA457@redhat.com> (raw)
These patches were part of series including BIOS fixes.
BIOS fixes has been applied, but it looks like qemu fixes
were forgotten. Reposting.
Reset BARs and a couple of other registers on bus reset, as per PCI
spec.
This fixes up posting v4 which was garbled, sorry about that.
Michael S. Tsirkin (2):
qemu: make cirrus init value pci spec compliant
qemu: cleanup unused macros in cirrus
hw/cirrus_vga.c | 36 ------------------------------------
1 files changed, 0 insertions(+), 36 deletions(-)
next reply other threads:[~2009-11-30 19:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-30 19:02 Michael S. Tsirkin [this message]
2009-12-01 0:02 ` [Qemu-devel] Re: [PATCHv5-repost 0/2] qemu: cirrus reset-related fixes Juan Quintela
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=20091130190219.GA457@redhat.com \
--to=mst@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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).