From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=56603 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PiTwI-0004of-I6
	for qemu-devel@nongnu.org; Thu, 27 Jan 2011 10:39:15 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <alevy@redhat.com>) id 1PiTwH-00077v-EI
	for qemu-devel@nongnu.org; Thu, 27 Jan 2011 10:39:14 -0500
Received: from mx1.redhat.com ([209.132.183.28]:28025)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <alevy@redhat.com>) id 1PiTwH-00077k-68
	for qemu-devel@nongnu.org; Thu, 27 Jan 2011 10:39:13 -0500
Date: Thu, 27 Jan 2011 17:39:06 +0200
From: Alon Levy <alevy@redhat.com>
Message-ID: <20110127153905.GC19334@playa.tlv.redhat.com>
References: <4D416F07.6060604@redhat.com>
	<20110127151211.GB19334@playa.tlv.redhat.com>
	<4D419018.8080901@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4D419018.8080901@redhat.com>
Subject: [Qemu-devel] Re: [Spice-devel] paravirtual mouse/tablet, v5
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: Peter Hutterer <peter.hutterer@who-t.net>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, spice-devel <spice-devel@lists.freedesktop.org>

On Thu, Jan 27, 2011 at 04:32:40PM +0100, Gerd Hoffmann wrote:
>   Hi,
> 
> >>typedef struct qemu_pvmouse_ack {
> >>     uint32_t features; /* qemu_pvtable_features */
> >
> >Why does this comment say "qemu_pvtable_features" and the one above
> >says "qemu_pvmouse_features"?
> 
> Not intentional, will fix.  Leftover because it is misspelled (t in
> table*t* missing), so the search+replace didn't catch it.
> 
> >>};
> >>
> >>
> >>enum qemu_pvmouse_axis_type {
> >>     /* absolute */
> >>     QEMU_PVMOUSE_AXIS_POS_X = 1,
> >>     QEMU_PVMOUSE_AXIS_POS_Y,
> >>     QEMU_PVMOUSE_AXIS_PRESSURE,
> >>
> >
> >So is the concensus to not treat 3d mice as core protocol?
> >just a AXIS_POS_Z and AXIS_REL_Z I think would be simple to
> >add. Running cad apps in a vm seems possible.
> 
> That list isn't meant to be complete, I'll happily take suggestions
> for axises we should add here.  *_Z for a 3d mouse certainly is
> reasonable.
> 
> >What's the outcome of the discussion with Peter? wasn't there
> >a suggestion to send information from the host to the guest about
> >monitor configuration, so guest can do inverse to send correct
> >coordinates to host?
> 
> Yep.  I think that isn't something for the pvmouse but for vdagent
> though.  In the simplest case make VDAgentMonitorsConfig
> bidirectional, so the guest can send feedback to the spice client
> and inform how the actual configuration looks like.
> 

Ok, sounds good.

> cheers,
>   Gerd
> 
> _______________________________________________
> Spice-devel mailing list
> Spice-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/spice-devel