From: Vojtech Pavlik <vojtech@suse.cz>
To: dean gaudet <dean-list-linux-kernel@arctic.org>
Cc: Stefan Reinauer <stepan@suse.de>,
linux-kernel@vger.kernel.org, Andries Brouwer <aebr@win.tue.nl>
Subject: Re: 2.6.0-test2 has i8042 mux problems
Date: Tue, 12 Aug 2003 22:56:42 +0200 [thread overview]
Message-ID: <20030812205642.GD23011@ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.53.0307280927590.18444@twinlark.arctic.org>
On Mon, Jul 28, 2003 at 09:38:15AM -0700, dean gaudet wrote:
> On Mon, 28 Jul 2003, Stefan Reinauer wrote:
>
> > * dean gaudet <dean-list-linux-kernel@arctic.org> [030728 04:13]:
> > > 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.
>
> that's slightly different than what i get without i8042_nomux, and a
> keyboard & mouse plugged in, the system crashes and burns badly during
> boot. without the keyboard and mouse it boots fine.
>
> with i8042_nomux it's a lot happier.
>
> my system is a test board for a new processor with the ali1563 -- which is
> a newer hypertransport variant of the 1533/1535. i'm not sure yet if
> there are production boards with the 1563. but it's nice to know it
> happens with your 1533 as well.
Hmm, I think I may have a similar bridge around ... I'll try.
> andries -- i'll send you a copy of the in/out traffic (it's a bit large
> for posting).
>
> -dean
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Vojtech Pavlik
SuSE Labs, SuSE CR
prev parent reply other threads:[~2003-08-12 20:56 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
2003-07-28 16:38 ` dean gaudet
2003-08-12 20:56 ` Vojtech Pavlik [this message]
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=20030812205642.GD23011@ucw.cz \
--to=vojtech@suse.cz \
--cc=aebr@win.tue.nl \
--cc=dean-list-linux-kernel@arctic.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stepan@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.