xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: andr2000@gmail.com, owen.smith@citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH] kbdif: Define "feature-raw-pointer" and "request-raw-pointer"
Date: Tue, 18 Jul 2017 21:41:24 -0400	[thread overview]
Message-ID: <20170719014124.GB25303@localhost.localdomain> (raw)
In-Reply-To: <alpine.DEB.2.10.1707181528330.17537@sstabellini-ThinkPad-X260>

On Tue, Jul 18, 2017 at 03:29:14PM -0700, Stefano Stabellini wrote:
> On Mon, 3 Jul 2017, Stefano Stabellini wrote:
> > On Mon, 3 Jul 2017, Owen Smith wrote:
> > > Backends set "feature-raw-pointer" if its capable of reporting
> > > absolute positions without scaling the coordinates to screen
> > > size. This should be set during the backend init.
> > > Frontends set "request-raw-pointer" to request that backends
> > > do not rescale absolute coordinates to screen size, and the
> > > coordinates remain in the range [0, 0x7fff]. This request is
> > > only applicable if "request-abs-pointer" is also set. Frontends
> > > should set this value before setting Connected.
> > > 
> > > Signed-off-by: Owen Smith <owen.smith@citrix.com>
> > 
> > Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
> 
> Konrad, are you OK with this? Can I go ahead and commit it?

Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> 
> 
> > 
> > > ---
> > > Adding this feature will help determine the difference between older
> > > backends and newer backends. In the case I'm interested in, the difference
> > > between old QEMU vkbd backend which blocks waiting for the vfb device, which
> > > is not present on HVM guests, and a newer QEMU backend that does not rely
> > > on display information to rescale axis values.
> > > 
> > >  xen/include/public/io/kbdif.h | 14 ++++++++++++++
> > >  1 file changed, 14 insertions(+)
> > > 
> > > diff --git a/xen/include/public/io/kbdif.h b/xen/include/public/io/kbdif.h
> > > index dcbd71a..3ce54e9 100644
> > > --- a/xen/include/public/io/kbdif.h
> > > +++ b/xen/include/public/io/kbdif.h
> > > @@ -63,6 +63,13 @@
> > >   *      Backends, which support reporting of multi-touch events
> > >   *      should set this to 1.
> > >   *
> > > + * feature-raw-pointer
> > > + *      Values:        <uint>
> > > + *
> > > + *      Backends, which support reporting raw (unscaled) absolute coordinates
> > > + *      for pointer devices should set this to 1. Raw (unscaled) values have
> > > + *      a range of [0, 0x7fff].
> > > + *
> > >   *------------------------- Pointer Device Parameters ------------------------
> > >   *
> > >   * width
> > > @@ -98,6 +105,13 @@
> > >   *
> > >   *      Request backend to report multi-touch events.
> > >   *
> > > + * request-raw-pointer
> > > + *      Values:         <uint>
> > > + *
> > > + *      Request backend to report raw unscaled absolute pointer coordinates.
> > > + *      This option is only valid if request-abs-pointer is also set.
> > > + *      Raw unscaled coordinates have the range [0, 0x7fff]
> > > + *
> > >   *----------------------- Request Transport Parameters -----------------------
> > >   *
> > >   * event-channel
> > > -- 
> > > 2.1.4
> > > 
> > 

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-07-19  1:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-03 12:57 [PATCH] kbdif: Define "feature-raw-pointer" and "request-raw-pointer" Owen Smith
2017-07-03 14:19 ` Paul Durrant
2017-07-03 23:49 ` Stefano Stabellini
2017-07-18 22:29   ` Stefano Stabellini
2017-07-19  1:41     ` Konrad Rzeszutek Wilk [this message]
2017-07-04  5:52 ` Oleksandr Andrushchenko

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=20170719014124.GB25303@localhost.localdomain \
    --to=konrad.wilk@oracle.com \
    --cc=andr2000@gmail.com \
    --cc=owen.smith@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xen.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).