From: Anthony Liguori <anthony@codemonkey.ws>
To: Dave Airlie <airlied@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] vmware fixes in a git tree
Date: Thu, 17 Dec 2009 10:45:01 -0600 [thread overview]
Message-ID: <4B2A600D.8070802@codemonkey.ws> (raw)
In-Reply-To: <21d7e9970912170240n58ec0350r70ac9327acd75182@mail.gmail.com>
Dave Airlie wrote:
> Hi guys,
>
> I've gotten vmware going again on master using some patches from
> Anthony (rebased onto master)
> and a fix for the cursor pixmap which was causing a segfault.
>
Excellent, I just ran into a bug report indicating that as the cause of
the seg fault.
> The patches are in
> git://people.freedesktop.org/~airlied/qemu.git vmware-queue
> http://cgit.freedesktop.org/~airlied/qemu/log/?h=vmware-queue
>
> I can send the queue to the list if required, including Anthony's patches.
>
Yes, please do.
> It also contains a fix to expose the fifo via a second PCI BAR which
> is what the vmware
> svga spec states.
>
> I've booted an F12 LiveCD with this.
>
Awesome, thanks!
Regards,
Anthony Liguori
> Dave.
>
>
>
prev parent reply other threads:[~2009-12-17 16:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 10:40 [Qemu-devel] vmware fixes in a git tree Dave Airlie
2009-12-17 16:45 ` Anthony Liguori [this message]
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=4B2A600D.8070802@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=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).