From: Gerd Hoffmann <kraxel@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: spice-devel <spice-devel@lists.freedesktop.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] paravirtual tablet v3
Date: Tue, 18 Jan 2011 14:46:30 +0100 [thread overview]
Message-ID: <4D3599B6.5050002@redhat.com> (raw)
In-Reply-To: <4D345A1F.6000607@codemonkey.ws>
Hi,
>> 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
Probably.
> 2) the host can do something useful with the
> information that the guest is not multitouch capable.
What do you think of here?
cheers,
Gerd
next prev parent reply other threads:[~2011-01-18 13:46 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
2011-01-18 13:46 ` Gerd Hoffmann [this message]
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=4D3599B6.5050002@redhat.com \
--to=kraxel@redhat.com \
--cc=anthony@codemonkey.ws \
--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).