From: Martin <madstitz@gmail.com>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: Re: Fwd: ALPS v7 TrackStick detected wrongly
Date: Fri, 15 Jan 2016 12:27:16 +0100 [thread overview]
Message-ID: <1452857236.32706.0@smtp.gmail.com> (raw)
In-Reply-To: <20160114200726.GW11560@pali>
So I can't be sure if it even detects the trackstick, because it just
creates the device anyway?
I bought the trackpad from eBay, as Lenovo doesn't sell it separately.
Apparently its pure luck if you get a Synaptics or Alps model - I got
the Alps, my friend got the Synaptics model.
Don't know whether Lenovo uses Alps in its newer series too or if this
trackpad is a fake (feels and works very real though ;))
Maybe I'll try to get a synaptics then, as this was the manufacturer of
the original trackpad.
Greetings
Martin
Am Do, 14. Jan, 2016 um 9:07 schrieb Pali Rohár <pali.rohar@gmail.com>:
> On Thursday 14 January 2016 13:04:43 Martin <madstitz@gmail.com>
> wrote:
>> Is your patch intended to solve this or should I open a bug ticket?
>
> Hi! That my patch hides Track Stick input device when ALPS touchpad
> report that Track Stick is not present. Before my patch was applied
> kernel created "AlpsPS/2 ALPS DualPoint Stick" input device for V7
> protocol always, even if there was no Track Stick device.
>
> But as Dmitry said, you replaced Synaptics touchpad with ALPS which is
> working differently. Synaptics touchpad export PS/2 bus via its own
> pass-though protocol and this bus then available on kernel which do
> normal PS/2 mouse detection it. So kernel bind thinkpad TPPS2 driver
> to
> that bus.
>
> ALPS is working differently. There is no pass-though mode and all data
> (touchpad, track stick) are exported in ALPS packets. Kernel ALPS
> driver
> has special parser which can decide if packet comes from touchpad or
> trackstick (based on received data). So via ALPS touchpad kernel
> cannot
> communicate directly with trackpoint.
>
> So I guess... in case you have thinkpad trackpoint HW and ALPS
> touchpad
> which cannot work with that trackpoint you just do not get trackpoint
> data. Here kernel cannot do anything.
>
> I suspect that if you apply my patch (which check presence of
> trackstick) then kernel probably do not export this track stick device
> "AlpsPS/2 ALPS DualPoint Stick" anymore...
>
>> I: Bus=0011 Vendor=0002 Product=0008 Version=0700
>> N: Name="AlpsPS/2 ALPS DualPoint Stick"
>> P: Phys=isa0060/serio1/input1
>> S: Sysfs=/devices/platform/i8042/serio1/input/input8
>> U: Uniq=
>> H: Handlers=mouse0 event6
>> B: PROP=21
>> B: EV=7
>> B: KEY=70000 0 0 0 0
>> B: REL=3
>
> --
> Pali Rohár
> pali.rohar@gmail.com
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-01-15 11:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1452773083.4165.0@smtp.gmail.com>
2016-01-14 12:11 ` Fwd: ALPS v7 TrackStick detected wrongly Pali Rohár
2016-01-14 19:34 ` Dmitry Torokhov
2016-01-15 11:50 ` Pali Rohár
2016-01-14 20:07 ` Fwd: " Pali Rohár
2016-01-15 11:27 ` Martin [this message]
2016-01-15 11:42 ` 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=1452857236.32706.0@smtp.gmail.com \
--to=madstitz@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=pali.rohar@gmail.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 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).