From: "Pali Rohár" <pali.rohar@gmail.com>
To: Juanito <juam+kernel@posteo.net>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
"masaki.ota@jp.alps.com" <masaki.ota@jp.alps.com>
Cc: linux-input@vger.kernel.org, Paul Donohue <linux-kernel@paulsd.com>
Subject: Re: ALPS touchpad ot correctly recognized: GlidePoint vs DualPoint
Date: Sat, 9 Sep 2017 10:36:06 +0200 [thread overview]
Message-ID: <201709091036.06899@pali> (raw)
In-Reply-To: <52f87b68-8a6b-1d9c-f341-1e488ff43441@posteo.net>
[-- Attachment #1: Type: Text/Plain, Size: 1626 bytes --]
On Saturday 09 September 2017 10:12:42 Juanito wrote:
> Hello,
>
> On 09/08/2017 08:48 AM, Pali Rohár wrote:
> > On Friday 08 September 2017 07:00:34 Juanito wrote:
> >>> ThinkPad with ALPS? Should not be it Synaptic? Maybe
> >>> miss-detection?
> >>
> >> Sorry, I forgot to mention this. The ThinkPad came with a clickpad
> >> I **really** disliked, so I bought this on the Internet.
> >
> > So, here is a problem. ThinkPads works with Synaptic touchpads, not
> > with ALPS.
>
> There definitely seems to be a problem here :)
>
> Do you mean that the alps code might not be detecting the trackpoint
> because probably the red thingie works with synaptics?
>
> So could this be the situation:
> ALPS driver: Hey touchpad! Do you have a trackstick?
> ALPS touchpad: No, I don't.
> AD: Ok! (and thinks 'I am going to have to ignore all trackstick
> packets that might arrive')
>
> So the driver understands that there can't possibly be any buttons
> because there is no trackstick?
IIRC ALPS touchpad hardware itself does not work with non-ALPS
trackpoint.
Masaki, any comments?
> >> If by trackstick you mean the red thingie, it is **not** working.
> >
> > Ok. And it is working with your patch?
>
> No, it isn't :(
I expected... You just created franken-hardware.
Looks like with your hack patch it is possible to make buttons working,
but I suspect that trackstick would.
Maybe Masaki can provide more information about this fact if we can do
anything.
Dmitry, what you as maintainer going to do with this problem?
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2017-09-09 8:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 7:05 ALPS touchpad ot correctly recognized: GlidePoint vs DualPoint Juanito
2017-09-07 21:31 ` Dmitry Torokhov
2017-09-07 21:54 ` Pali Rohár
2017-09-08 5:00 ` Juanito
2017-09-08 6:48 ` Pali Rohár
2017-09-09 8:12 ` Juanito
2017-09-09 8:36 ` Pali Rohár [this message]
2017-09-09 18:12 ` Dmitry Torokhov
2017-09-09 18:21 ` Juanito
2017-09-11 2:38 ` Masaki Ota
2017-09-11 11:26 ` Juanito
2018-02-04 18:16 ` Pali Rohár
[not found] ` <f291e382-b90e-baba-fb3c-bdebc991a21d@posteo.net>
2018-02-04 20:21 ` Pali Rohár
2018-02-05 7:48 ` Juanito
2018-02-05 11:19 ` Juanito
2018-02-11 23:01 ` Pali Rohár
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=201709091036.06899@pali \
--to=pali.rohar@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=juam+kernel@posteo.net \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@paulsd.com \
--cc=masaki.ota@jp.alps.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.