From: David Woodhouse <dwmw2@infradead.org>
To: Benson Chow <blc@q.dyndns.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: USB Keyboards for x86/uhci in 2.4- kernels?
Date: Wed, 10 Jan 2001 12:32:19 +0000 [thread overview]
Message-ID: <25542.979129939@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.31.0101091640470.21522-100000@q.dyndns.org>
In-Reply-To: <Pine.LNX.4.31.0101091640470.21522-100000@q.dyndns.org>
blc@q.dyndns.org said:
> In BIOS my USB keyboard works really poorly - it almost seems
> scancodes get dropped left and right. Ok, so I don't mind too much,
> i'm sure BIOS has a very limited driver. After booting Microsoft's
> offerring, it would work fine after it installs its driver. I also
> tried this same keyboard on a HPUX Visualize C3600 workstation and it
> also works nicely.
> However linux would never fix this "scancode drop" syndrome even
> after loading the hid or usbkbd driver.
I'm using a USB keyboard (on x86/uhci) without too much trouble.
Occasionally I seem to miss a key release event, causing the thing to
autorepeat until I hit the key and release it again.
Also, the behaviour on pressing multiple keys simultaneously seems to be
strange - 'grep' tends to come out as 'grerp' and 'mount' as 'mouunt' if I
type them fast enough. That may simply be the keyboard's fault though.
--
dwmw2
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-01-10 12:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 6:55 USB Keyboards for x86/uhci in 2.4- kernels? Benson Chow
2001-01-10 8:24 ` Greg KH
2001-01-10 11:49 ` Vojtech Pavlik
2001-01-10 15:15 ` Benson Chow
2001-01-10 12:32 ` David Woodhouse [this message]
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=25542.979129939@redhat.com \
--to=dwmw2@infradead.org \
--cc=blc@q.dyndns.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.