From: Vojtech Pavlik <vojtech@suse.cz>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
Andries Brouwer <aebr@win.tue.nl>,
A Guy Called Tyketto <tyketto@wizard.com>,
linux-kernel@vger.kernel.org
Subject: Re: kbd not functioning in 2.5.25-dj2
Date: Sun, 14 Jul 2002 20:17:11 +0200 [thread overview]
Message-ID: <20020714201711.A30723@ucw.cz> (raw)
In-Reply-To: <20020714191301.C3637@flint.arm.linux.org.uk>; from rmk@arm.linux.org.uk on Sun, Jul 14, 2002 at 07:13:01PM +0100
On Sun, Jul 14, 2002 at 07:13:01PM +0100, Russell King wrote:
> On Sun, Jul 14, 2002 at 08:01:19PM +0200, Vojtech Pavlik wrote:
> > On Sun, Jul 14, 2002 at 07:37:29PM +0200, Andries Brouwer wrote:
> > > Send 0xff to port 60. Wait for the 0xfa ack. Wait for the 0xaa good status.
> >
> > The problem is that 0xff takes too long to finish to be done while Linux
> > is booting, and it has already been done by the BIOS.
>
> Ah hem, "bios". Do we trust that hunk of proprietary code now? Note
> also that pc_keyb.c allowed for embedded devices where there is no BIOS.
> That said, not sending 0xff seems to be fine on the keyboards I have
> here. I wouldn't like to guarantee that it's fine across all keyboards
> though, just like sending 0xAA on reconnect isn't guaranteed.
Well, so far I've tested with about 20 different weird keyboards ...
let's see. If the future shows we need 0xff, there's no problem adding
it.
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2002-07-14 18:14 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-13 7:24 kbd not functioning in 2.5.25-dj2 Ed Sweetman
2002-07-13 7:37 ` A Guy Called Tyketto
2002-07-13 8:01 ` Ed Sweetman
2002-07-13 8:45 ` Ed Sweetman
2002-07-13 9:06 ` Vojtech Pavlik
2002-07-13 21:48 ` A Guy Called Tyketto
2002-07-14 8:05 ` Vojtech Pavlik
2002-07-14 10:18 ` A Guy Called Tyketto
2002-07-14 10:32 ` Russell King
2002-07-14 12:01 ` Vojtech Pavlik
2002-07-14 12:17 ` Andries Brouwer
2002-07-14 12:37 ` Vojtech Pavlik
2002-07-14 13:36 ` Rogier Wolff
2002-07-14 17:32 ` Vojtech Pavlik
2002-07-14 17:49 ` Russell King
2002-07-14 17:59 ` Vojtech Pavlik
2002-07-14 18:07 ` Russell King
2002-07-14 18:11 ` Vojtech Pavlik
2002-07-14 17:37 ` Andries Brouwer
2002-07-14 18:01 ` Vojtech Pavlik
2002-07-14 18:13 ` Russell King
2002-07-14 18:17 ` Vojtech Pavlik [this message]
2002-07-15 3:53 ` Maciej W. Rozycki
2002-07-14 21:30 ` A Guy Called Tyketto
2002-07-15 3:00 ` Vojtech Pavlik
2002-07-15 8:30 ` A Guy Called Tyketto
2002-07-15 7:28 ` Alexander Hoogerhuis
2002-07-15 10:56 ` Arnd Bergmann
2002-07-15 10:06 ` Alexander Hoogerhuis
2002-07-13 9:07 ` A Guy Called Tyketto
2002-07-13 9:32 ` Vojtech Pavlik
2002-07-13 9:04 ` Russell King
-- strict thread matches above, loose matches on Subject: below --
2002-07-15 15:45 Rudmer van Dijk
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=20020714201711.A30723@ucw.cz \
--to=vojtech@suse.cz \
--cc=aebr@win.tue.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=tyketto@wizard.com \
/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.