From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Stephen Evanchik <evanchsa@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Synaptics and TrackPoint problems in 2.6.12
Date: Wed, 20 Jul 2005 01:17:33 -0500 [thread overview]
Message-ID: <200507200117.33852.dtor_core@ameritech.net> (raw)
In-Reply-To: <a71293c2050719204047bd2afe@mail.gmail.com>
On Tuesday 19 July 2005 22:40, Stephen Evanchik wrote:
> Dimitry,
>
> I have been receiving a lot of complaints that TrackPoints on
> Synaptics pass-thru ports stopped working with 2.6.12. I retested
> 2.6.9 and 2.6.11-rc3 successfully, I believe 2.6.11.7 may also work
> but that is unconfirmed at this point.
>
> The behavior is always the same .. after sending the read secondary ID
> command, the TrackPoint seems to be disabled from that point forward.
>
> Any ideas?
>
Not really... You know, I am reviewing the 2.6.12 patch and don't really
see anything that might have caused the problem you are describing. I know
that not all devices on pass-through ports are broken since I have one
(not TrackPoint, just a simple eraser head pointer) and I make sure it
works ;)
When you are talking about reading secondary ID, are you talking about
TP_READ_ID or something else?
Are you experiencing the breakage yourself? It might be interesting to
see the log with i8042 debugging turned on.
--
Dmitry
next prev parent reply other threads:[~2005-07-20 6:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-20 3:40 Synaptics and TrackPoint problems in 2.6.12 Stephen Evanchik
2005-07-20 6:17 ` Dmitry Torokhov [this message]
2005-07-20 14:34 ` Sergey Vlasov
2005-07-20 15:05 ` Dmitry Torokhov
2005-07-20 15:46 ` Sergey Vlasov
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=200507200117.33852.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=evanchsa@gmail.com \
--cc=linux-kernel@vger.kernel.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