From: Marko Macek <Marko.Macek@gmx.net>
To: vojtech@suse.cz, thoffman@arnor.net
Cc: vanackere@lif.univ-mrs.fr, linux-kernel@vger.kernel.org
Subject: USB input ati_remote autorepeat problem
Date: Tue, 27 Jun 2006 21:51:20 +0200 [thread overview]
Message-ID: <44A18C38.7040504@gmx.net> (raw)
Hello!
I have problems with autorepeat in ati_remote (drivers/usb/input) driver
in "recent" kernels: all keys start repeating immediately without some
delay.
This makes some things, like changing the channel prev/next or toggling
fullscreen, etc... impossible/hard.
The problem seems to be related to FILTER_TIME and HZ=250 (which I
forgot to change).
FILTER_TIME is defined to HZ / 20, and since 250 is not divisible by 20,
the time will be too short to ignore enough events.
Defining FILTER_TIME to HZ / 20 + 1 seems to fix things, but I'm not
sure if there are any bad side effects.
Mark
next reply other threads:[~2006-06-27 19:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 19:51 Marko Macek [this message]
2006-06-27 20:09 ` USB input ati_remote autorepeat problem John Daiker
2006-06-27 21:46 ` Nish Aravamudan
2006-06-28 6:52 ` Vojtech Pavlik
2006-07-02 18:37 ` Marko Macek
2006-07-02 19:18 ` 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=44A18C38.7040504@gmx.net \
--to=marko.macek@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=thoffman@arnor.net \
--cc=vanackere@lif.univ-mrs.fr \
--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