From: Richard Hirst <rhirst@linuxcare.com>
To: Thomas Marteau <marteaut@esiee.fr>
Cc: "parisc-linux@parisc-linux.org" <parisc-linux@parisc-linux.org>
Subject: Re: [parisc-linux] The final patch for the keyboard problem
Date: Wed, 8 Aug 2001 00:31:23 +0100 [thread overview]
Message-ID: <20010808003123.G1011@linuxcare.com> (raw)
In-Reply-To: <20010807131419.B1011@linuxcare.com>; from rhirst@linuxcare.com on Tue, Aug 07, 2001 at 01:14:19PM +0100
On Tue, Aug 07, 2001 at 01:14:19PM +0100, Richard Hirst wrote:
> On Tue, Aug 07, 2001 at 11:58:17AM +0100, Richard Hirst wrote:
> > Anyway, I'm about to try it on a couple of machines here; I'll let you
> > know how it goes.
>
> HP US keyboard on B180. Worked until I unplugged and replugged the
> keyboard. Keyboard was dead after that, but machine still responded
> to pings.
Tried unplugging/replugging again; survived this time. Keyboard
generates a scancode AA (reconnected), but the console says unrecognised
scancode 7f.
btw, I guess we should reinitialise the LED status on a replug.
Back to the compaq UK keyboard, CapsLock works also with the longer
mdelay() calls. The CapsLock LED doesn't come on, but the others
do, so I'll assume faulty k/b for now. Unplug/replug still results
in a dead keyboard (init=/bin/sh, so I can't tell if the machine is
still alive).
On the mdelay() calls, the PC driver would check for an ack every 1ms,
but would only resend the command every 1000ms. Your code was resending
every 1ms. Checking every 1ms and resending less frequently is better
than just checking and resending every 5ms.
Richard
next prev parent reply other threads:[~2001-08-07 23:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-07 7:27 [parisc-linux] The final patch for the keyboard problem Thomas Marteau
2001-08-07 10:58 ` Richard Hirst
2001-08-07 12:14 ` Richard Hirst
2001-08-07 21:36 ` Richard Hirst
2001-08-09 16:45 ` Grant Grundler
2001-08-07 23:31 ` Richard Hirst [this message]
2001-08-07 16:23 ` Matthew Wilcox
2001-08-10 17:23 ` Richard Hirst
2001-08-13 18:09 ` marteau
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=20010808003123.G1011@linuxcare.com \
--to=rhirst@linuxcare.com \
--cc=marteaut@esiee.fr \
--cc=parisc-linux@parisc-linux.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.