From: ebiederm@xmission.com (Eric W. Biederman)
To: Vojtech Pavlik <vojtech@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.3-bk7 i8042 does not work on a genuine i386 ibm ps/2 model 70.
Date: 03 Mar 2004 13:30:53 -0700 [thread overview]
Message-ID: <m1wu61wu4i.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <m1znax3gsq.fsf@ebiederm.dsl.xmission.com>
Ok I made time and here is what I found out with respect to 2.4.21
By default 2.4.x does not reset the keyboard so the IBM PowerPC portable
work around does not even run.
/*
* In case we run on a non-x86 hardware we need to initialize both the
* keyboard controller and the keyboard. On a x86, the BIOS will
* already have initialized them.
*
* Some x86 BIOSes do not correctly initialize the keyboard, so the
* "kbd-reset" command line options can be given to force a reset.
* [Ranger]
*/
#ifdef __i386__
int kbd_startup_reset __initdata = 0;
#else
int kbd_startup_reset __initdata = 1;
#endif
However I added he kbd-reset command line along with print
statements to be certain it happened.
The bit XLAT did not get set. That register stayed at a
value of 0x25. The PowerPC portable work around was activated.
And my keyboard still worked.
So perhaps the fix then is to attempt to set that bit and if
you can't set it assume it is always in the XLAT state?
To be very clear the problem I see on 2.6 is since it sees
XLAT disabled it does XLAT in software in
drivers/input/keyboard/atkbd.c
Eric
next prev parent reply other threads:[~2004-03-03 20:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-29 14:32 Eric W. Biederman
2004-03-03 10:13 ` Vojtech Pavlik
2004-03-03 14:05 ` David Weinehall
2004-03-03 14:12 ` Vojtech Pavlik
2004-03-03 18:51 ` Eric W. Biederman
2004-03-03 20:30 ` Eric W. Biederman [this message]
2004-03-04 6:45 ` [PATCH] 2.6.4-rc1 make i8042 " Eric W. Biederman
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=m1wu61wu4i.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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®