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: Wed, 22 Feb 2006 17:13:26 -0500 [thread overview]
Message-ID: <d120d5000602221413i19aac43cv43820051f2de9c7@mail.gmail.com> (raw)
In-Reply-To: <20060222220954.GA7930@suse.cz>
On 2/22/06, Vojtech Pavlik <vojtech@suse.cz> wrote:
> On Wed, Feb 22, 2006 at 04:09:33PM -0500, Dmitry Torokhov wrote:
> > > How about simply this patch instead?
> > >
> > > Setting autorepeat will not be possible on 'dumb' keyboards anymore by
> > > default, but since these usually are special forms of hardware anyway,
> > > like the DRAC3, this shouldn't be an issue for most users. Using
> > > 'softrepeat' on these keyboards will restore the behavior for users that
> > > need it.
> >
> > I am not keen on changing the default behaviour... How many dumb
> > keyboards are out there?
>
> Apart from the DRAC3, some home-made Sun-to-PS2 converter, and a single
> non-x86 embedded box, I don't recall anything. Answer: very few.
>
> There may be users, though, that use this option to force the detection
> of the keyboard when not really plugged in, eg. for flaky KVMs. I've
> Googled for that usage, but found none.
>
> > I'd rather turn atkbd.softrepeat into a 3-state switch...
>
> We could, but the more I think about it, the stronger I'm convinced that
> the dumbkbd => softrepeat => softraw option implication chain is wrong.
> The second implication is necessary, but with dumbkbd it's quite likely
> you won't want softraw.
>
OK, then I'll schedule this change for 2.6.17 and we'll see if anyone screams.
--
Dmitry
next prev parent reply other threads:[~2006-02-22 22:13 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
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 [this message]
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=d120d5000602221413i19aac43cv43820051f2de9c7@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®