linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Santiago Gala <sgala@apache.org>,
	Hans de Goede <hdegoede@redhat.com>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Input: ALPS - Detect trackstick presence for v7 protocol
Date: Sat, 28 Mar 2015 09:51:06 +0100	[thread overview]
Message-ID: <201503280951.06399@pali> (raw)
In-Reply-To: <20150328034335.GA9145@dtor-ws>

[-- Attachment #1: Type: Text/Plain, Size: 2009 bytes --]

On Saturday 28 March 2015 04:43:35 Dmitry Torokhov wrote:
> On Sat, Mar 28, 2015 at 01:30:58AM +0000, Santiago Gala wrote:
> > The behaviour is the same with 3.19.1 as with 4.0.0-rc5 +
> > the patched psmouse you give me. The difference in lsinput
> > is just name and current position:
> > 
> > $ diff -u alps06.txt alps11-new.txt
> > --- alps06.txt  2015-03-18 07:21:08.827315595 +0100
> > +++ alps11-new.txt      2015-03-27 21:24:44.285503438 +0100
> > @@ -1,5 +1,5 @@
> > 
> >  # EVEMU 1.2
> > 
> > -# Input device name: "AlpsPS/2 ALPS DualPoint TouchPad"
> > +# Input device name: "AlpsPS/2 ALPS GlidePoint"
> > 
> >  # Input device ID: bus 0x11 vendor 0x02 product 0x08
> >  version 0x700 # Supported events:
> >  #   Event type 0 (EV_SYN)
> > 
> > @@ -15,14 +15,14 @@
> > 
> >  #     Event code 335 (BTN_TOOL_QUADTAP)
> >  #   Event type 3 (EV_ABS)
> >  #     Event code 0 (ABS_X)
> > 
> > -#       Value   1076
> > +#       Value   1549
> > 
> >  #       Min        0
> >  #       Max     4095
> >  #       Fuzz       0
> >  #       Flat       0
> >  #       Resolution 42
> >  #     Event code 1 (ABS_Y)
> > 
> > -#       Value    869
> > +#       Value    877
> > 
> >  #       Min        0
> >  #       Max     2047
> >  #       Fuzz       0
> > 
> > @@ -59,7 +59,7 @@
> > 
> >  # Properties:
> >  #   Property  type 0 (INPUT_PROP_POINTER)
> >  #   Property  type 2 (INPUT_PROP_BUTTONPAD)
> > 
> > -N: AlpsPS/2 ALPS DualPoint TouchPad
> > +N: AlpsPS/2 ALPS GlidePoint
> > 
> >  I: 0011 0002 0008 0700
> >  P: 05 00 00 00 00 00 00 00
> >  B: 00 0b 00 00 00 00 00 00 00
> 
> Hmm, if resolution is the same I wonder if we are dropping
> some packets... Is there any messages from psmouse module in
> dmesg?
> 
> Thanks.
> 

For me output/diff looks ok. Name is based on DUALPOINT flag 
which is cleared for non trackstick device version. And my patch 
adding that trackstick detection for v7.

-- 
Pali Rohár
pali.rohar@gmail.com

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2015-03-28  8:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-22 13:46 [PATCH] Input: ALPS - Detect trackstick presence for v7 protocol Pali Rohár
2015-03-23 11:39 ` Hans de Goede
2015-03-23 17:02   ` Pali Rohár
2015-03-24  7:27     ` Hans de Goede
     [not found]       ` <CAPXTYCXrvFDbvEDkEQxkcJ5y1OHx7Ldm+bu-LnWfigjTj6gECw@mail.gmail.com>
2015-03-24 16:46         ` Pali Rohár
2015-03-24 17:01         ` Dmitry Torokhov
2015-03-29  3:59       ` Dmitry Torokhov
2015-05-28  7:39         ` Pali Rohár
     [not found] ` <201503271816.11723@pali>
     [not found]   ` <CAPXTYCX13Y7FY7o9CPPQXchSVYiJ415o_yxOFruO-scTV=X27w@mail.gmail.com>
2015-03-27 20:08     ` Pali Rohár
     [not found]       ` <CAPXTYCVGpm27naqu723f8kC0h75TT6XSN0X_EWCu6cXJS0G2kg@mail.gmail.com>
2015-03-27 20:54         ` Pali Rohár
     [not found]           ` <CAPXTYCUqibXqTBf8VKGKixKeM49LhucxFDhS+04fUsiSEKMKOg@mail.gmail.com>
2015-03-28  3:43             ` Dmitry Torokhov
2015-03-28  8:51               ` Pali Rohár [this message]
2016-01-05 16:44 ` Pali Rohár
2016-01-06  8:12   ` Hans de Goede
2016-01-06 23:55     ` Dmitry Torokhov

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=201503280951.06399@pali \
    --to=pali.rohar@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sgala@apache.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).