From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Vojtech Pavlik <vojtech@suze.cz>,
torvalds@osdl.org, vojtech@ucw.cz, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 24/44] Workaround i8042 chips with broken MUX mode
Date: Sat, 27 Mar 2004 19:40:39 -0500 [thread overview]
Message-ID: <200403271940.39940.dtor_core@ameritech.net> (raw)
In-Reply-To: <20040328002938.GA11657@wsdw14.win.tue.nl>
On Saturday 27 March 2004 07:29 pm, Andries Brouwer wrote:
> On Tue, Mar 16, 2004 at 10:24:09AM -0800, Dmitry Torokhov wrote:
> > Vojtech Pavlik wrote:
>
> > > + /* Workaround for broken chips which seem to
> > support MUX, but in reality don't. */
>
> Why call them "broken"? Better to delete that word.
>
> > > + /* They all report version 12.10 */
> > > + if (mux_version == 0xCA)
> > > + return -1;
> >
> > I think it should be 0xAC (0xA4 with 4th bit flipped)
> > as the version reported is 10.12.
>
> Yes. I have seen one such report. Have there been more?
>
As it turned out its not the chip but USB legacy emulation that
gets in the way of synaptics query. Actually alot of problems were
linked to broken legacy emulation implementations, Vojtech mentioned
that PCI quirk to turn legacy emulation off may be appropriate.
> The Synaptics multiplexing proposal uses 0xf0, 0x56, 0xa4
> to activate and 0xf0, 0x56, 0xa5 to deactivate.
> In both cases the replies must be 0xf0, 0x56, version.
>
> Thus, I suppose one might get a more robust detection
> by checking that both the activation and deactivation
> sequences yield the same version.
>
Unfortunately in this particular case it looks like something flips
4th bit on some (but not all, like every 3rd) bytes, so it may very
well respond with 0xAC to both queries.
--
Dmitry
next prev parent reply other threads:[~2004-03-28 0:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-16 18:24 [PATCH 24/44] Workaround i8042 chips with broken MUX mode Dmitry Torokhov
2004-03-18 20:37 ` Vojtech Pavlik
[not found] ` <200403190005.36956.dtor_core@ameritech.net>
2004-03-19 13:58 ` Vojtech Pavlik
2004-03-19 14:21 ` Stefan Smietanowski
2004-03-19 14:30 ` Vojtech Pavlik
2004-03-19 13:56 ` Vojtech Pavlik
2004-03-28 0:29 ` Andries Brouwer
2004-03-28 0:40 ` Dmitry Torokhov [this message]
2004-03-28 1:25 ` Andries Brouwer
2004-03-28 3:11 ` Dmitry Torokhov
2004-03-28 7:45 ` Stefan Smietanowski
-- strict thread matches above, loose matches on Subject: below --
2004-03-16 14:19 [PATCH 23/44] Use __obsolete_setup() in input drivers to warn about obsolete kernel params Vojtech Pavlik
2004-03-16 14:19 ` [PATCH 24/44] Workaround i8042 chips with broken MUX mode Vojtech Pavlik
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=200403271940.39940.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=aebr@win.tue.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=vojtech@suze.cz \
--cc=vojtech@ucw.cz \
/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