Hello,

On 09/08/2017 08:48 AM, Pali Rohár wrote:

On Friday 08 September 2017 07:00:34 Juanito wrote:

quoted

quoted

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?

quoted

If by trackstick you mean the red thingie, it is **not** working.

Ok. And it is working with your patch?

No, it isn't :(

quoted

quoted

quoted

quoted

I am not sure if the device is actually a DualPoint or not (I
don't really understand the terminology here), but the thing is
that the buttons work when the kernel believes it to be one.

This is the info I have managed to find about the device while
running on the non-working debian:

dmesg:
[    2.914806] input: AlpsPS/2 ALPS GlidePoint as
/devices/platform/i8042/serio1/input/input2

lsinput:
/dev/input/event11

   bustype : BUS_I8042
   vendor  : 0x2
   product : 0x8
   version : 1792
   name    : "AlpsPS/2 ALPS GlidePoint"
   phys    : "isa0060/serio1/input0"
   bits ev : (null) (null) (null)

I have played around with the drivers/input/mouse/alps.c file and
found out the following:

e7 and ec are important (although I don't know what these are
exactly) and have the following values:

e7: 73 03 0a
ec: 88 b0 13

Masaki should know exact type of device...