From: Andries Brouwer <aebr@win.tue.nl>
To: Claas Langbehn <claas@rootdir.de>
Cc: dean gaudet <dean-list-linux-kernel@arctic.org>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test2 has i8042 mux problems
Date: Tue, 29 Jul 2003 00:58:38 +0200 [thread overview]
Message-ID: <20030728225838.GA1845@win.tue.nl> (raw)
In-Reply-To: <20030728210910.GA832@rootdir.de>
On Mon, Jul 28, 2003 at 11:09:10PM +0200, Claas Langbehn wrote:
> Hello!
>
> its strange. After switching debug on, it suddenly works.
Maybe the timing changed?
[It would also be nice to see a log where things failed.
Probably syslog would still work.]
> Below my debug info.
Thanks! Let me comment it.
-------------------------------------------------------------
check_mux: First we probe for a Synaptics mux. Find none.
check_aux: Then we probe for a PS/2 mouse port. Find one.
Good. Found something. Call serio_register_port().
This searches for attached devices.
We know already that it is the PS/2 mouse port, but who knows
what might be connected. Let us try all devices we know about.
Is it perhaps a keyboard?
> drivers/input/serio/i8042.c: d4 -> i8042 (command) [0]
> drivers/input/serio/i8042.c: f2 -> i8042 (parameter) [0]
We wait for 99 jiffies, but no keyboard ID shows up.
Then try to set LEDs.
> drivers/input/serio/i8042.c: d4 -> i8042 (command) [99]
> drivers/input/serio/i8042.c: ed -> i8042 (parameter) [99]
> drivers/input/serio/i8042.c: fe <- i8042 (interrupt, aux, 0, timeout) [99]
Get an error back. This mouse doesnt want to set its LEDs.
Is it perhaps a mouse?
> drivers/input/serio/i8042.c: d4 -> i8042 (command) [113]
> drivers/input/serio/i8042.c: f2 -> i8042 (parameter) [113]
No mouse ID either. No devices connected to this port, but
at least we have a port:
> serio: i8042 AUX port at 0x60,0x64 irq 12
Then we continue, and check the keyboard side of the i8042 controller.
Things work satisfactorily, we detect a keyboard.
Silly enough we set it to scancode Set 2, but nevertheless give
commands that are only meaningful for scancode Set 3.
Keyboards that know only about Set 2 will be unhappy.
> input: AT Set 2 keyboard on isa0060/serio0
> serio: i8042 KBD port at 0x60,0x64 irq 1
OK, found keyboard.
-------------------------------------------------------------
So far the story of your debug file.
What is your actual hardware? Is there a mouse?
Andries
next prev parent reply other threads:[~2003-07-28 22:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 2:13 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 [this message]
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=20030728225838.GA1845@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=claas@rootdir.de \
--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
all inboxes | Powered by JetHome®