From: Claas Langbehn <claas@rootdir.de>
To: Andries Brouwer <aebr@win.tue.nl>
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: Mon, 28 Jul 2003 22:35:23 +0200 [thread overview]
Message-ID: <20030728203523.GA857@rootdir.de> (raw)
In-Reply-To: <20030728113626.GA1706@win.tue.nl>
> Interesting. Yes, the new keyboard driver knows far too much about
> keyboards, and that knowledge is right only in 98% of the cases.
> No doubt we'll be forced to back out a lot of probing done now.
>
> Nevertheless it would be interesting to see precisely what happens.
> Could you try to change the #undef DEBUG in drivers/input/serio/i8042.c
> into #define DEBUG and report what output you get at boot time?
This is the only debug message i can see without keyboard.
serio: i8042 AUX Port at 0x60,0x64 irq 12
input: AT set2 keyboard on isa0060/serio0
serio i8042 KBD port at 0x60,0x64 irq 1
Can you tell me how to force the driver to enable my keyboard anyways?
It would be great, because booting is a pain right now.
Regards, claas
next prev parent reply other threads:[~2003-07-28 20:42 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 [this message]
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=20030728203523.GA857@rootdir.de \
--to=claas@rootdir.de \
--cc=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 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.