WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] RFC: drop frontend support for relative pointer

To: Markus Armbruster <armbru@xxxxxxxxxx>
Subject: Re: [Xen-devel] RFC: drop frontend support for relative pointer
From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Date: Wed, 14 Oct 2009 13:42:58 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Daniel P. Berrange" <berrange@xxxxxxxxxx>, Jean Guyader <jean.guyader@xxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>
Delivery-date: Wed, 14 Oct 2009 05:42:56 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <87ws2y2mwg.fsf@xxxxxxxxxxxxxxxxx>
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: <87vdirw2d8.fsf@xxxxxxxxxxxxxxxxx> <alpine.DEB.2.00.0910071829490.25583@kaball-desktop> <20091007200124.GD2270@xxxxxxxxxx> <alpine.DEB.2.00.0910081221070.11437@kaball-desktop> <87skduoxbo.fsf@xxxxxxxxxxxxxxxxx> <f68b66460910121102p1239f7fdveaa154906ca5e5d9@xxxxxxxxxxxxxx> <f68b66460910121131u634cab5dya30f47958431149c@xxxxxxxxxxxxxx> <87d44ss5su.fsf@xxxxxxxxxxxxxxxxx> <f68b66460910121418t35c4e4camb714ebbdb82c52cb@xxxxxxxxxxxxxx> <87ocobcm9j.fsf@xxxxxxxxxxxxxxxxx> <alpine.DEB.2.00.0910131720120.22447@kaball-desktop> <87bpkbb1rk.fsf@xxxxxxxxxxxxxxxxx> <alpine.DEB.2.00.0910141256070.11134@kaball-desktop> <87ws2y2mwg.fsf@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Alpine 2.00 (DEB 1167 2008-08-23)
On Wed, 14 Oct 2009, Markus Armbruster wrote:
> Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> writes:
> 
> > On Tue, 13 Oct 2009, Markus Armbruster wrote:
> >> Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> writes:
> >> 
> >> > On Tue, 13 Oct 2009, Markus Armbruster wrote:
> >> >> > I don't really thing we could use absolute because we do graphic
> >> >> > device pass through with PV guest and the resolution we have on the
> >> >> > screen is completely decouple with the fb resolution.
> >> >> 
> >> >> I figure the real solution is to decouple the PV pointer/keyboard from
> >> >> the PV framebuffer, so you can configure the pointer independently, and
> >> >> don't have to drag a PV framebuffer along, just to get a PV
> >> >> pointer/keyboard.
> >> >> 
> >> >
> >> > True, but it still wouldn't solve the problem of dropping relative mouse
> >> > coordinates support from vkbd.
> >> 
> >> You can always convert between relative and absolute in the backend.
> >> Pointer resolution need not match the graphics resolution (think tablet,
> >> not touchscreen).
> >> 
> >> Nevertheless, it might be more convenient for this use case to keep
> >> relative around.  Then the backend need only be able to convert from
> >> absolute to relative (for frontends declining feature-abs-pointer), not
> >> the other direction.  XCI is of course free to require a frontend that
> >> doesn't decline.
> >> 
> >> If we decide to keep relative, we need to restructure pointer frontend
> >> initialization to each axis either relative or absolute.  Unless evdev
> >> developers find a way to continue coping with both.
> >> 
> >
> > Given that absolute->relative conversion is not very good, I think it is
> > best to keep relative alive.
> 
> Unless you mean relative->absolute, you're not making sense to me :)
>

Yes I meant relative->absolute, sorry for the confusion.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel