All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Markus Armbruster <armbru@redhat.com>
Subject: Re: RFC: drop frontend support for relative pointer
Date: Thu, 8 Oct 2009 12:32:21 +0100	[thread overview]
Message-ID: <20091008113221.GF17867@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0910081221070.11437@kaball-desktop>

On Thu, Oct 08, 2009 at 12:25:23PM +0100, Stefano Stabellini wrote:
> On Wed, 7 Oct 2009, Daniel P. Berrange wrote:
> > That's good to know - stubdom was one area I was concerned about. To the
> > best of my knowledge the only backend that ever sent relative mouse events
> > was the old PVFB we had in Fedora 6 which was the original code before 
> > the eventual merge into official xen-devel trees. So official repos have
> > always defaulted to absolute mode.  Hopefully no one out there has gone
> > and re-implemented the PVFB backend in any other fork of Xen and dropped
> > ABS mode or made REL the default ???
> > 
> > IMHO if ABS mode is able to work correctly, then there's absolutely no
> > benefit in having a REL mode at all, so its best deleted / removed. 
> 
> I guess keeping around unused code doesn't make much sense but I was just
> being cautious, given that for example XCI is currently using relative
> coordinates so they are not dead just yet.

Doh, that was exactly the kind of issue I was afraid of. If there is
a current host OS that uses relative mode, then we can't get rid of it
in the frontend. So if XCI only does relative mode, that pretty much
puts a stop to Markus' plan

Daniel
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

  reply	other threads:[~2009-10-08 11:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-07 17:16 RFC: drop frontend support for relative pointer Markus Armbruster
2009-10-07 17:39 ` Stefano Stabellini
2009-10-07 18:16   ` Markus Armbruster
2009-10-07 20:01   ` Daniel P. Berrange
2009-10-08 11:25     ` Stefano Stabellini
2009-10-08 11:32       ` Daniel P. Berrange [this message]
2009-10-08 12:59       ` Markus Armbruster
2009-10-12 18:02         ` Jean Guyader
2009-10-12 18:31           ` Jean Guyader
2009-10-12 20:42             ` Markus Armbruster
2009-10-12 21:18               ` Jean Guyader
2009-10-13 16:05                 ` Markus Armbruster
2009-10-13 16:21                   ` Stefano Stabellini
2009-10-13 18:13                     ` Markus Armbruster
2009-10-13 20:58                       ` Jean Guyader
2009-10-14 11:56                       ` Stefano Stabellini
2009-10-14 12:14                         ` Markus Armbruster
2009-10-14 12:42                           ` Stefano Stabellini
2009-10-09 17:33       ` Markus Armbruster
2009-10-12 17:27         ` Stefano Stabellini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091008113221.GF17867@redhat.com \
    --to=berrange@redhat.com \
    --cc=armbru@redhat.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.