From: Dave Airlie <airlied@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] qemu fixup patch sequence.
Date: Fri, 18 Dec 2009 08:08:05 +1000 [thread overview]
Message-ID: <1261087691-8319-1-git-send-email-airlied@gmail.com> (raw)
First patch adds a second PCI BAR as per the VMware SVGA specification for
the fifo instead of using the top of the VRAM BAR.
Patches 2-5 are from Anthony and I just rebased them on top of master.
Patch6: fixes a crasher in vmware when X starts inside the guest.
I've booted these with an F12 LiveCD and all seems to work.
Dave.
next reply other threads:[~2009-12-17 22:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 22:08 Dave Airlie [this message]
2009-12-17 22:08 ` [Qemu-devel] [PATCH 1/6] vmware: setup PCI BAR 2 for FIFO as per vmware spec Dave Airlie
2009-12-17 22:08 ` [Qemu-devel] [PATCH 2/6] Make sure to enable dirty tracking of VBE vram mapping Dave Airlie
2009-12-17 22:08 ` [Qemu-devel] [PATCH 3/6] Make sure to enable dirty log tracking for VMware VGA Dave Airlie
2009-12-17 22:08 ` [Qemu-devel] [PATCH 4/6] Fix VMware VGA depth computation Dave Airlie
2009-12-17 22:08 ` [Qemu-devel] [PATCH 5/6] VMware VGA: Only enable dirty log tracking when fifo is disabled Dave Airlie
2009-12-17 22:08 ` [Qemu-devel] [PATCH 6/6] vmware: increase cursor buffer size Dave Airlie
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=1261087691-8319-1-git-send-email-airlied@gmail.com \
--to=airlied@gmail.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).