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

On Fri, Sep 26, 2003 at 12:41:38PM +0200, Nicolas Mailhot wrote:
> Le ven 26/09/2003 ? 12:24, Vojtech Pavlik a écrit :
> > On Fri, Sep 26, 2003 at 11:43:43AM +0200, Nicolas Mailhot wrote:
> > > Vojtech Pavlik  wrote:
> 
> [...]
> 
> > > 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.
> > 
> > You do. Scrolling up/down in a document is one example. And there is no
> > point to limit the repeat to say 80 or 200 characters. You would still
> > hate having 80 repeated characters and then it stopping.
> 
> Well then only allow monster autorepeats for arrows then.
> (they are never stuck in my board anyway;)
> 
> > The problem really is there is no way to detect it. My latest patches
> > should fix this for AT keyboards by not using software autorepeat for
> > them.
> > 
> > Of course this won't fix any problems with USB, if there are still any.
> > My USB keyboard works just perfectly, no problems with the autorepeat.
> 
> Well mine doesn't:(. I seem to have gathered from past threads that HID
> makes the full keyboard status available at all time (unlike AT which
> only provides push/release events). Couldn't the repeat code just
> double-check the key is really stuck every ten repeats for example ?

It provides the full state when the state changes. If you miss the
change on release ...

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  reply	other threads:[~2003-09-26 10:51 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-26  9:43 Keyboard oddness Nicolas Mailhot
2003-09-26 10:24 ` Vojtech Pavlik
2003-09-26 10:41   ` Nicolas Mailhot
2003-09-26 10:51     ` Vojtech Pavlik [this message]
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=20030926105121.GA9334@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=Nicolas.Mailhot@laposte.net \
    --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 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).