From: Andries Brouwer <aebr@win.tue.nl>
To: dean gaudet <dean-list-linux-kernel@arctic.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test2 has i8042 mux problems
Date: Mon, 28 Jul 2003 05:59:20 +0200 [thread overview]
Message-ID: <20030728035920.GA1660@win.tue.nl> (raw)
In-Reply-To: <Pine.LNX.4.53.0307271906020.18444@twinlark.arctic.org>
On Sun, Jul 27, 2003 at 07:13:26PM -0700, dean gaudet wrote:
> this was a bug i reported back a few versions as well -- and i don't think
> i received any responses (nor from the maintainer).
>
> i've got a box on which 2.4.x works fine, but 2.6.0-test2 gets into a snit
> when it's trying to initialize the i8042. i can get 2.6.0-test2 to boot
> if i add "i8042_nomux".
>
> the mux initialization code seems kind of ... wonk -- it seems to write
> values to the registers then read back and if the value is the same then
> it assumes the mux is there. that seems way too likely to be broken in
> situations when the mux isn't there... it'd be better to be looking for
> some value which is different after writing.
No, it writes f0, 56, a4 and if it gets f0, 56, and not a4, then it assumes
there is a mux.
[This is a Synaptics convention.]
What hardware do you have? And what is the conversation?
next prev parent reply other threads:[~2003-07-28 3:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 2:13 2.6.0-test2 has i8042 mux problems dean gaudet
2003-07-28 3:59 ` Andries Brouwer [this message]
2003-07-29 22:51 ` dean gaudet
2003-07-30 0:25 ` Andries Brouwer
2003-07-28 5:26 ` Claas Langbehn
2003-07-28 11:36 ` Andries Brouwer
2003-07-28 20:35 ` Claas Langbehn
2003-07-28 21:09 ` Claas Langbehn
2003-07-28 22:58 ` Andries Brouwer
2003-07-29 7:53 ` Claas Langbehn
2003-07-28 14:29 ` Stefan Reinauer
2003-07-28 16:38 ` dean gaudet
2003-08-12 20:56 ` 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=20030728035920.GA1660@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=dean-list-linux-kernel@arctic.org \
--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