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


Re: [Xen-devel] pvfb: Absolute vs relative mouse tracking mystery

To: Joshua West <jwest@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] pvfb: Absolute vs relative mouse tracking mystery
From: John Haxby <john.haxby@xxxxxxxxxx>
Date: Tue, 10 Aug 2010 17:20:24 +0100
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 10 Aug 2010 09:22:26 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C58B5DD.6030003@xxxxxxxxxxxx>
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: <4BE49501.6000408@xxxxxxxx> <alpine.DEB.2.00.1005101537310.11380@kaball-desktop> <4BE86945.9050408@xxxxxxxx> <alpine.DEB.2.00.1005111154050.11380@kaball-desktop> <20100619154145.GM17817@xxxxxxxxxxx> <4C1CE6DE.8000602@xxxxxxxx> <4C1F7DC4.3090706@xxxxxxxxxx> <4C1F7E58.8030605@xxxxxxxx> <4C55C6CD.40200@xxxxxxxxxxxx> <4C5715C9.3030006@xxxxxxxx> <4C571E88.3050704@xxxxxxxxxxxx> <4C571F20.5010903@xxxxxxxx> <768613C6-FA1E-455A-A2EF-183E69AEA517@xxxxxxxxxx> <4C58B5DD.6030003@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100720 Fedora/3.1.1-1.fc13 Lightning/1.0b2pre Thunderbird/3.1.1
 On 04/08/10 01:35, Joshua West wrote:
Ahh... So then if we get the PVFB going with 1024x768 resolution, instead of wonderful 1990's 800x600, we're all set ;-)

Did you ever have one of those plastic pantographs when you were a kid? I remember having a couple and they were rubbish, the enlarged (or reduced) drawing looked nothing like the original. The mapping from absolute to relative in mousedev has the same sort of problem, although if I'm feeling really generous it might just be rounding errors (though I doubt it).

I've been testing with evdev driver as well (Option "Device" "/dev/input/event1" for me), but that has not worked. I see what you're saying though - I can see two entries in /proc/bus/input/devices, and my mouse handlers are "mouse0 event1 ts0", but both the keyboard and mouse physical device is the same: "xen/device/vkbd/0". And this is all with linux-2.6.18-xen.hg.

Hmm. It should work. I don't have a linux-2.6.18-xen.hg handy, but if you send me your xorg.conf and /proc/bus/input/devices (off list) I'll take a look.

I'm looking forward to your custom RHEL/CentOS driver to get this going.

Sorting it out now.

One last question -- even if using linux-2.6.18-xen.hg, are you saying we still need request-abs-pointer kernel argument? Wasn't that just to enable absolute pointer mode in the RHEL mouse driver if using RHEL 5.5 and their Xen kernel (looked that way from their patch)? Or is RHEL's Xorg somehow also looking for this directive?

It's just in the Red Hat/CentOS 5.5 kernels, you don't need it for any of the others. And it's just to get the xenkbd front end to set request-abs-pointer in xenstore. For my money, it would be better to have absolute pointers by default and have guests ask for relative ones if they really really want them. I think this was propose a little while ago, but I don't recall what happened.


Xen-devel mailing list