From: Vojtech Pavlik <vojtech@suse.cz>
To: Sau Dan Lee <danlee@informatik.uni-freiburg.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.7-bk way too fast
Date: Mon, 21 Jun 2004 17:17:39 +0200 [thread overview]
Message-ID: <20040621151738.GA1351@ucw.cz> (raw)
In-Reply-To: <xb7r7s9nj2c.fsf@savona.informatik.uni-freiburg.de>
On Mon, Jun 21, 2004 at 03:20:59PM +0200, Sau Dan Lee wrote:
> Vojtech> It's possible that X does it's own autorepeat, though
> Vojtech> that'd rather surprise me.
>
> Why? XFree86 has been doing its own autorepeat, I think.
>
> $ xset q
> Keyboard Control:
> auto repeat: on key click percent: 0 LED mask: 00000000
> auto repeat delay: 660 repeat rate: 25
> auto repeating keys: 00ffffffdffffbbf
> fa9fffffffdfe5ff
> ffffffffffffffff
> ffffffffffffffff
> bell percent: 50 bell pitch: 400 bell duration: 100
>
> And I can change it via "xset r rate [delay [rate ]]", according to
> "xset help". Indeed, you can use 'xset' to change the rate/delay to
> very extreme values, which exceed the hardware allowed on AT/PS2
> keyboards (e.g. rates > 30 cps), adjusted with the 'kbdrate' command.
> So, the only possibility for these hardware limits to be transcended
> is s/w based autorepeat.
Indeed, X does its own autorepeat.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2004-06-21 15:17 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 13:20 2.6.7-bk way too fast Sau Dan Lee
2004-06-21 15:17 ` Vojtech Pavlik [this message]
2004-06-21 15:25 ` Sau Dan Lee
-- strict thread matches above, loose matches on Subject: below --
2004-06-21 2:54 Jeff Garzik
2004-06-21 3:29 ` Ricky Beam
2004-06-21 7:20 ` Felipe Alfaro Solana
2004-06-21 8:23 ` Vojtech Pavlik
2004-07-02 7:53 ` David Woodhouse
2004-07-02 12:56 ` Vojtech Pavlik
2004-06-21 3:36 ` Jeff Garzik
2004-06-21 3:49 ` Matt H.
2004-06-21 11:53 ` Marcel Holtmann
2004-06-21 3:52 ` Zwane Mwaikambo
2004-06-21 3:55 ` Zwane Mwaikambo
2004-06-21 4:02 ` Andrew Morton
2004-06-21 5:00 ` Norberto Bensa
2004-06-21 5:39 ` Norberto Bensa
2004-06-21 6:16 ` Linus Torvalds
2004-06-21 7:05 ` Clemens Schwaighofer
2004-06-21 7:18 ` Matt H.
2004-06-21 7:16 ` Andrew Morton
2004-06-21 8:15 ` Matt H.
2004-06-21 8:20 ` Clemens Schwaighofer
2004-06-21 9:25 ` Clemens Schwaighofer
2004-06-21 10:24 ` Felipe Alfaro Solana
2004-06-21 7:37 ` Linus Torvalds
2004-06-21 9:52 ` Jeff Sipek
2004-06-21 16:41 ` Jeff Sipek
2004-06-21 7:19 ` Jeff Sipek
2004-06-21 5:11 ` Jeff Garzik
2004-06-21 5:08 ` Aubin LaBrosse
2004-06-21 8:22 ` Vojtech Pavlik
2004-06-21 10:26 ` Felipe Alfaro Solana
2004-06-21 11:02 ` Vojtech Pavlik
2004-06-21 8:48 ` Andrew Morton
2004-06-21 9:17 ` Matt H.
2004-06-21 9:56 ` Jeff Sipek
2004-06-21 10:47 ` Felipe Alfaro Solana
2004-06-21 16:55 ` Norberto Bensa
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=20040621151738.GA1351@ucw.cz \
--to=vojtech@suse.cz \
--cc=danlee@informatik.uni-freiburg.de \
--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