archive mirror
 help / color / mirror / Atom feed
From: Stefan Reinauer <>
To: dean gaudet <>
Cc:, Andries Brouwer <>
Subject: Re: 2.6.0-test2 has i8042 mux problems
Date: Mon, 28 Jul 2003 16:29:52 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

* dean gaudet <> [030728 04:13]:
> 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.
> the southbridge in this system is the ali1563.  if it helps i can supply a
> complete trace of in/out on ports 0x60 and 0x64.
I can confirm this. I have an Amilo A laptop with the following sb:
00:07.0 ISA bridge: ALi Corporation M1533 PCI to ISA Bridge [Aladdin IV]

without "i8042_nomux" the keyboard is recognized fine, but no mouse is
found on the mux. With the option everything works fine.


  parent reply	other threads:[~2003-07-28 14:16 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
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 [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).