From: "andrzej zaborowski" <balrog@zabor.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Guest mouse cursor drawing in SDL
Date: Tue, 20 Mar 2007 17:06:02 +0100 [thread overview]
Message-ID: <fb249edb0703200906u5c996434p77209a88b614c484@mail.gmail.com> (raw)
In-Reply-To: <45FFFFF2.3090702@codemonkey.ws>
On 20/03/07, Anthony Liguori <anthony@codemonkey.ws> wrote:
> Thiemo Seufer wrote:
> > andrzej zaborowski wrote:
> >
> >> This should allow the emulated video cards that support hardware
> >> accelerated cursors to relay the cursor drawing to host, possibly
> >> using real hardware cursor. This way the guest and host effectively
> >> share one cursor. Only SDL support is included. Not tested with mice
> >> that report absolute coordinates.
> >>
> >> The cursor does not appear in the framebuffer seen by the guest, it's
> >> only drawn on the host. One funny effect is that it's not clipped to
> >> the size of the framebuffer and can stick out of the SDL window.
> >>
> >> I think the sdl.c could use a small rewrite to have all cursor hiding
> >> and showing in one place instead of spread across the file.
> >>
> >> VNC support would need employing an extension for this, according to
> >> Anthony Liguori. VMware made a documented VNC extension that does it.
> >>
> >
> >
> >> From 3cf77a8b3c80b0306a0e73677ac6faeb1f83e0a2 Mon Sep 17 00:00:00 2001
> >> From: Andrzej Zaborowski <balrog@zabor.org>
> >> Date: Sun, 11 Mar 2007 15:31:12 +0100
> >> Subject: [PATCH] Host-accelerated mouse cursor support in SDL.
> >>
> >
> > This patch breaks scrolling in the cirrus vga framebuffer.
> >
I will try to see why it breaks scrolling after I fix the VMware SVGA.
It shouldn't affect anything other than the mouse cursor, and only
when enabled by the SVGA.
>
> I think we want to expose these functions via DisplayState. It would be
> nice if the semantics of too were similar to the rest of the functions
Agreed. They should be accessed through ds->mouse_set.
> > (the pixel format of the cursor was the same as the pixel format of
> DisplayState).
I'm not sure if we want to always use the same pixel format - for
example with VMware SVGA and SDL in 16 bit mode, the cursor pixel
format reported by guest Xorg was 8 bpp. This would mean two
conversions instead of one: first VMware SVGA would have to convert 8
-> 16 bpp then SDL 16 -> 1 bpp.
> One question in my mind is what the alpha mask should look like. All
> that VNC (and SDL) can use is a 1-bit alpha depth. That's all Cirrus
> supports too. VMware SVGA supports an 8-bit alpha channel though so it
> may make sense to design the interface now to support that.
VMware SVGA without CAP_ALPHA_CURSOR also does only 1-bit alpha. Maybe
we should keep two masks - if the frontend (e.g SDL) supports only
1-bit alpha it would use only this basic mask - if the emulated VGA
supports only 1-bit alpha it would leave the other mask opaque.
Regards,
Andrzej
next prev parent reply other threads:[~2007-03-20 16:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-11 14:19 [Qemu-devel] [PATCH] Guest mouse cursor drawing in SDL andrzej zaborowski
2007-03-20 15:08 ` Thiemo Seufer
2007-03-20 15:38 ` Anthony Liguori
2007-03-20 16:06 ` andrzej zaborowski [this message]
2007-03-21 1:28 ` Anthony Liguori
2007-03-23 13:57 ` andrzej zaborowski
2007-03-25 23:49 ` Anthony Liguori
2007-03-26 20:30 ` andrzej zaborowski
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=fb249edb0703200906u5c996434p77209a88b614c484@mail.gmail.com \
--to=balrog@zabor.org \
--cc=balrogg@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).