This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: [PATCH] input/xen-fbfront: advertise either absolute or

To: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH] input/xen-fbfront: advertise either absolute or relative coordinates
From: Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx>
Date: Sat, 12 Mar 2011 22:24:11 -0800
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, Olaf Hering <olaf@xxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, linux-input@xxxxxxxxxxxxxxx
Delivery-date: Sun, 13 Mar 2011 07:25:03 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=oOA6/BzfXlc7mS1J7Qw8XyXEDYXwBuiI2j4zUf6gDJI=; b=Y09znBWS/7naVoSfOOrjs1N/0S0u2pMgLh99RRQ59VkANq1O8dAfr+0+1EAgdZVKh/ NaMvO59rpnJKtqlkokw3d2nRzJOaPEQD8vgtxeK3ZlButTfFUJlOTIG1s0FwAdpPkYp4 Iwjsf5QZk+pz9SxoDu6Q8Tsf8QfPuq4oBFf4A=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=jRQFsWH6LxyT7YWpDxV/0FtTXW+hxJtrRbTmuH2iNoCXEPU3wexA2MRGKeRFF3pW5v qRGK92avmk9QoT4MJpUdJb+Ilq7zjcrE7UWtNBU6ySmWKCSBf1s6+9G09AFEZEZm262s RMEKU/CVpC4OzXB+qwVaFOxgy+ntJxAMWVtg8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <alpine.DEB.2.00.1103111124400.2968@kaball-desktop>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <alpine.DEB.2.00.1103111124400.2968@kaball-desktop>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.21 (2010-09-15)
Hi Stefano,

On Fri, Mar 11, 2011 at 11:30:10AM +0000, Stefano Stabellini wrote:
> From: Olaf Hering <olaf@xxxxxxxxx>
> A virtualized display device is usually viewed with the vncviewer
> application, either by 'xm vnc domU' or with vncviewer localhost:port.
> vncviewer and the RFB protocol provides absolute coordinates to the
> virtual display. These coordinates are either passed through to a PV
> guest or converted to relative coordinates for a HVM guest.
> A PV guest receives these coordinates and passes them to the kernels
> evdev driver. There it can be picked up by applications such as the
> xorg-input drivers. Using absolute coordinates avoids issues such as
> guest mouse pointer not tracking host mouse pointer due to wrong mouse
> acceleration settings in the guests X display.
> Advertise either absolute or relative coordinates to the input system
> and the evdev driver, depending on what dom0 provides. The xorg-input
> driver prefers relative coordinates even if a devices provides both.

So if I am reading this correctly the original version handled changes
in backend capabilities and could switch between delivering either
relative or absolute coordinates. The new version selects the
capabilities at boot time and sticks with them. Was it really the
intended behavior?

BTW, drivers/input is intended for core input and handlers stuff with
drivers suppsed to be in drivers/input/<type>. Would you mind if I moved
this driver to drivers/input/misc?



Xen-devel mailing list