qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: spice-devel <spice-devel@lists.freedesktop.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] paravirtual tablet v3
Date: Mon, 17 Jan 2011 09:02:55 -0600	[thread overview]
Message-ID: <4D345A1F.6000607@codemonkey.ws> (raw)
In-Reply-To: <4D33FB99.6080207@redhat.com>

On 01/17/2011 02:19 AM, Gerd Hoffmann wrote:
> On 01/14/11 21:48, Anthony Liguori wrote:
>> On 01/14/2011 10:35 AM, Gerd Hoffmann wrote:
>>> Hi,
>>>
>>> Now v3 featuring multitouch ;)
>>>
>>> cheers,
>>> Gerd
>>
>> I really think multitouch needs to be a feature such that the guest can
>> nack it and the host can adjust accordingly. If it's there from day 1,
>> that's fine, but it still should be a feature.
>>
>> There are a lot of non-multitouch aware guests out there and I don't
>> think we want the driver to be the one deciding how to map a multitouch
>> device to something that doesn't support mulitouch.
>
> Sure, someone needs to map multitouch to non-multitouch.  I'd leave 
> that job to the guest driver tough.  Why do you think doing it in the 
> host is better?

My assumptions are 1) the host is capable of doing the mapping just as 
easily as the guest 2) the host can do something useful with the 
information that the guest is not multitouch capable.

Regards,

Anthony Liguori

>
> cheers,
>   Gerd
>

  reply	other threads:[~2011-01-17 15:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-14 16:35 [Qemu-devel] paravirtual tablet v3 Gerd Hoffmann
2011-01-14 20:48 ` Anthony Liguori
2011-01-17  8:19   ` Gerd Hoffmann
2011-01-17 15:02     ` Anthony Liguori [this message]
2011-01-18 13:46       ` Gerd Hoffmann
2011-01-18 15:20         ` Anthony Liguori

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=4D345A1F.6000607@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=spice-devel@lists.freedesktop.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).