From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=37351 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Pe4uk-00032n-D2
	for qemu-devel@nongnu.org; Sat, 15 Jan 2011 07:07:27 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <alevy@redhat.com>) id 1Pe4uj-0008NS-3Q
	for qemu-devel@nongnu.org; Sat, 15 Jan 2011 07:07:26 -0500
Received: from mx1.redhat.com ([209.132.183.28]:44296)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <alevy@redhat.com>) id 1Pe4ui-0008NI-RX
	for qemu-devel@nongnu.org; Sat, 15 Jan 2011 07:07:25 -0500
Date: Sat, 15 Jan 2011 14:07:18 +0200
From: Alon Levy <alevy@redhat.com>
Subject: Re: [Qemu-devel] paravirtual mouse/tablet
Message-ID: <20110115120717.GA10693@playa.redhat.com>
References: <4D2ED1C8.7070304@redhat.com> <4D2F1FA3.5030701@codemonkey.ws>
	<4D2F24EE.6070505@redhat.com> <4D2F2AB3.4020907@codemonkey.ws>
	<C1B91D17-6069-4E4C-9258-440800881A96@suse.de>
	<4D30332F.2070003@redhat.com>
	<108D35F5-7E49-4598-8903-599190A885E1@suse.de>
	<4D306819.80405@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4D306819.80405@redhat.com>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, spice-devel <spice-devel@lists.freedesktop.org>, Alexander Graf <agraf@suse.de>, Avi Kivity <avi@redhat.com>

On Fri, Jan 14, 2011 at 04:13:29PM +0100, Gerd Hoffmann wrote:
>   Hi,
> 
> >So it'd end up being (x,y,pressure) N times (I think 16 is fine for
> >the foreseeable future).
> 
> I'd tend to extend MOVE to (x,y,pressure,index) and send N events
> with the same timestamp.  Needs to send only as many events as it
> finds fingers on the touchpad, i.e. usually just one or two, even if
> the protocol can easily handle alot more than 16 ;)

Doesn't that lose the coincidence? I expect mostly presses happen
sequentially (milliseconds apart maybe, but still), so probably not
an issue at all.

> 
> For a simple tablet pressure and index would just be 0.
> 
> >The details of what exactly that means
> >should be figured out by the guest driver.
> 
> Agree.
> 
> >I'm not familiar with the hardware interface, but in order to support
> >that the background interface must be a lot more complex than a
> >simple button press.
> 
> Buttons events are for buttons.  Real ones, which apple lost ;)
> 
> Of course a tap on the trackpad is usually interpreted as mouse
> click. But that is the job of the guest OS, our virtual hardware
> doesn't care.
> 
> >But then again - how would we forward fine-grained scrolling to the
> >guest if we only know that it's scrolling, but not what the actual
> >presses on the touchpad looked like? Ugh.
> 
> There must be an interface to get (more or less) the raw touchpad
> data, for apps which want implement their own multitouch gestures?
> 
> cheers,
>   Gerd
> 
>