mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: "Vojtech Pavlik" <vojtech@suse.cz>
Cc: "Pete Zaitcev" <zaitcev@redhat.com>,
	linux-kernel@vger.kernel.org, stuart_hayes@dell.com
Subject: Re: Suppressing softrepeat
Date: Tue, 21 Feb 2006 16:32:21 -0500	[thread overview]
Message-ID: <d120d5000602211332p16381c16t100f93116cd33539@mail.gmail.com> (raw)
In-Reply-To: <20060221210800.GA12102@suse.cz>

On 2/21/06, Vojtech Pavlik <vojtech@suse.cz> wrote:
> On Tue, Feb 21, 2006 at 12:43:08PM -0800, Pete Zaitcev wrote:
>
> > Add the "nosoftrepeat" parameter. This is useful if a "dumb" keyboard
> > has (unswitcheable) hardware repeat, like in Dell DRAC3.
>
> The softrepeat code should properly ignore all autorepeated keys from a
> 'dumb' keyboard. It's rather common that a keyboard we can't communicate
> with is in autorepeat mode, because that's the mode AT keyboards wake up
> in after power on.

Hmm, atkbd only detects "repeated" keystrokes if it is working in
hard-repeat mode:

        value = atkbd->release ? 0 :
                                (1 + (!atkbd->softrepeat &&
test_bit(atkbd->keycode[code], atkbd->dev->key)));

Should we always recognize "repeats"? Then we woudl not need any
workarounds, be it kbdrate or sysfs.

--
Dmitry

  reply	other threads:[~2006-02-21 21:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-21 20:43 Pete Zaitcev
2006-02-21 21:08 ` Vojtech Pavlik
2006-02-21 21:32   ` Dmitry Torokhov [this message]
2006-02-21 21:40     ` Vojtech Pavlik
2006-02-21 21:57       ` Dmitry Torokhov
2006-02-22 20:00   ` Pete Zaitcev
2006-02-22 20:40     ` Vojtech Pavlik
2006-02-22 21:09       ` Dmitry Torokhov
2006-02-22 22:09         ` Vojtech Pavlik
2006-02-22 22:13           ` Dmitry Torokhov
2006-02-22 21:16       ` Pete Zaitcev
2006-02-21 21:15 ` Dmitry Torokhov
2006-02-21 21:35   ` Vojtech Pavlik
2006-02-22 20:46 Stuart_Hayes

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=d120d5000602211332p16381c16t100f93116cd33539@mail.gmail.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stuart_hayes@dell.com \
    --cc=vojtech@suse.cz \
    --cc=zaitcev@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®