linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Mailhot <Nicolas.Mailhot@laposte.net>
To: linux-kernel@vger.kernel.org
Cc: Vojtech Pavlik <vojtech@suse.cz>
Subject: Re: Keyboard oddness.
Date: Fri, 26 Sep 2003 11:43:43 +0200	[thread overview]
Message-ID: <1064569422.21735.11.camel@ulysse.olympe.o2t> (raw)

[-- Attachment #1: Type: text/plain, Size: 1282 bytes --]

Vojtech Pavlik  wrote:

|> Many people have reported missing key releases, and, as a consequence
| of that,
| > stuck keys. Your reports feel a bit different: the e0 is sometimes lost from
| > a key press, sometimes from a key release.

| I'm wondering if it could be a bug in the i8042.c driver ...

This is worse than that. I'm seing the same kind of bug on a pure HID+EHCI setup 
and I've seen other reports of USB problems on the lists these past months.

I can't just believe everyone and his cat has suddenly a faulty/broken keyboard.

The fact is software autorepeat seems extremely brittle in 2.6 and goes nuts every
once in a while for *everyone* (and I also seem to remember this was not always the 
case - the first 2.5 I tried didn't go mad on my setup this only happened later in 
2.5.7x times I think). Now maybe the underlying keyboard drivers are feeding it junk
I don't know but this is no justification for the way it's been misbehaving (crap 
hardware happens, glitchy hardware is common but the autorepeat code seems to expect
ideal behaviour that only happens on paper)

Couldn't it at least detect there's a problem ? Most people I know do not press a key
2000+ times in a row during normal activity.

Cheers,

-- 
Nicolas Mailhot

[-- Attachment #2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2003-09-26  9:43 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-26  9:43 Nicolas Mailhot [this message]
2003-09-26 10:24 ` Keyboard oddness Vojtech Pavlik
2003-09-26 10:41   ` Nicolas Mailhot
2003-09-26 10:51     ` Vojtech Pavlik
2003-09-26 12:48     ` jw schultz
2003-09-26 13:08     ` Nicolas Mailhot
2003-09-26 13:41       ` Vojtech Pavlik
2003-09-26 14:12         ` Nicolas Mailhot
2003-09-26 14:17           ` Vojtech Pavlik
2003-09-26 14:21             ` Nicolas Mailhot
2003-09-26 14:26               ` Vojtech Pavlik
2003-09-26 14:50                 ` Nicolas Mailhot
2003-09-26 15:06                   ` Vojtech Pavlik
2003-09-26 15:21                     ` Nicolas Mailhot
2003-09-26 15:24                       ` Vojtech Pavlik
2003-09-26 13:56       ` Helge Hafting
2003-09-26 14:01         ` Mike Dresser
2003-09-28 10:58           ` Helge Hafting
2003-10-02 12:40             ` Pavel Machek
2003-10-01 10:09   ` Pavel Machek
2003-10-01 13:06     ` Nicolas Mailhot
  -- strict thread matches above, loose matches on Subject: below --
2003-09-20 20:33 Rob Landley
2003-09-20 22:18 ` Andries Brouwer
2003-09-21 18:51   ` Rob Landley
2003-09-21 10:04 ` Vojtech Pavlik
2003-09-21 20:20   ` Rob Landley
2003-09-22 20:06   ` Rob Landley
2003-09-22 22:06     ` Andries Brouwer
2003-09-23  0:23       ` Rob Landley
2003-09-23 10:51         ` Greg Louis
2003-09-25 23:59       ` Rob Landley
2003-09-26  1:27       ` Rob Landley
2003-09-26  8:15         ` Andries Brouwer
2003-09-26  8:43           ` Rob Landley
2003-09-26  8:46           ` 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=1064569422.21735.11.camel@ulysse.olympe.o2t \
    --to=nicolas.mailhot@laposte.net \
    --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;
as well as URLs for NNTP newsgroup(s).