On 01/18/2011 07:46 AM, Gerd Hoffmann wrote:
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
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 us
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 accordi
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, b
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.
T
Hi,
Now v3 featuring multitouch ;)
cheers,
Gerd
#ifndef __QEMU_PVTABLET__
#define __QEMU_PVTABLET__ 1
/*
* qemu patavirtual tablet interface
*/
#include
/*
* our virtio-serial channel name(s)
*/
#define QEMU_PVTABLET_FORMAT "org.qemu.pvtablet.%d"
enum qemu_pvtablet_type {
QEMU_P
