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: Tue, 29 Jul 2003 09:53:07 +0200 [thread overview]
Message-ID: <20030729075307.GA914@rootdir.de> (raw)
In-Reply-To: <20030728225838.GA1845@win.tue.nl>
Hello!
> [It would also be nice to see a log where things failed.
> Probably syslog would still work.]
I cannot reproduce the error any more :(
It seems to work now. But dont ask my why.
> So far the story of your debug file.
> What is your actual hardware? Is there a mouse?
There is no PS/2 mouse. There is only the Keytronic KT-452
keyboard. Its about 14 years old and its switchable between
AT and XT. And it has a DIN-Plug. I am using an adaptor.
I just opend it and now i write you the chips inside it:
K450A/452A R.O.C.
PCB NO.P1.810133.01
EIC-8 94HB
big chip:
1. COPAM-8649B
2204R14 9018KE
SCN8049H
(c) Intel 1977
(m) signetics
smaller chips:
2. TI 035 CS
SN74LS125AN
MALAYSIA
3. 74LS138N
2103J30
9018EG
The other keyboard that always worked has this chip inside:
P8052AH 9706
9419
STC-02A
INTEL (c) 1980
-- claas
next prev parent reply other threads:[~2003-07-29 7:53 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 [this message]
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=20030729075307.GA914@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.