From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Manoj <manoj.iyer@canonical.com>
Cc: linux-input@vger.kernel.org
Subject: Re: Lenovo X220 Touchpad + Trackpoint BIOS issue workaround ?
Date: Tue, 5 Apr 2011 11:30:01 -0700 [thread overview]
Message-ID: <20110405183001.GC13086@core.coreip.homeip.net> (raw)
In-Reply-To: <4D9B5807.9090406@canonical.com>
On Tue, Apr 05, 2011 at 12:57:27PM -0500, Manoj wrote:
>
> >When both are enabled in BIOS what protocol does the kernel use to talk
> >to the touchpad? Does it use synaptics protocol?
>
> Yes it uses Synaptics TouchPad.
>
> if (max_proto > PSMOUSE_PS2 && synaptics_detect(p .. etc...
>
> I should say here that the trackpoint is not detected. And sometimes
> (very random) the trackpad is detected as PS/2 Mouse when touchpad
> and trackpoint are enabled in the BIOS... here is what it looks like
> in dmesg when it shows up as PS/2 Mouse instead of TPPS/2 IBM
> TrackPoint.
>
> [ 9.797624] input: ThinkPad Extra Buttons as
> /devices/platform/thinkpad_acpi/input/input8
> [ 10.480034] serio: Synaptics pass-through port at isa0060/serio1/input0
> [ 10.536122] input: SynPS/2 Synaptics TouchPad as
> /devices/platform/i8042/serio1/input/input9
> [ 34.507201] input: PS/2 Generic Mouse as
> /devices/platform/i8042/serio1/serio2/input/input10
>
Ah, so we do know that the touchpad has a pass-through port.
I guess you can try booting with i8042.debug with touchpad enabled and
disabled and see where exactly we fail to enable trackpoint the the
former case.
--
Dmitry
next prev parent reply other threads:[~2011-04-05 18:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 14:53 Lenovo X220 Touchpad + Trackpoint BIOS issue workaround ? Manoj
2011-04-05 17:32 ` Manoj
2011-04-05 17:39 ` Dmitry Torokhov
2011-04-05 17:57 ` Manoj
2011-04-05 18:30 ` Dmitry Torokhov [this message]
2011-04-05 22:02 ` Manoj
2011-04-05 22:19 ` Manoj
2011-04-05 22:40 ` Manoj
2011-04-06 17:03 ` Manoj
2011-04-06 17:12 ` 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=20110405183001.GC13086@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=manoj.iyer@canonical.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).