From: Vojtech Pavlik <vojtech@suse.cz>
To: dtor_core@ameritech.net
Cc: Pete Zaitcev <zaitcev@redhat.com>,
linux-kernel@vger.kernel.org, stuart_hayes@dell.com
Subject: Re: Suppressing softrepeat
Date: Tue, 21 Feb 2006 22:35:25 +0100 [thread overview]
Message-ID: <20060221213525.GA12526@suse.cz> (raw)
In-Reply-To: <d120d5000602211315y60ad2861n4cd64535f9f4850d@mail.gmail.com>
On Tue, Feb 21, 2006 at 04:15:57PM -0500, Dmitry Torokhov wrote:
> I see the problem but I don't think we want another module parameter
> for it. I think if you put the following somewhere into init scripts
> it shoudl work without any additional changes:
>
> echo -n "0" > /sys/bus/serio/devices/serioX/softrepeat
This should work, indeed, as an alternative to 'kbdrate -d 750'.
> Of couurse one would jhave to locate proper serioX but that should be easy.
>
> I also see the following in bugzilla: "... This causs a problem on
> systems that have no real keyboard plugged in, since atkbd probes for
> the keyboard, and won't take control of the port if it doesn't see
> one." Usually it is OK for keyboard to be missing as long as BIOS
> itself does not disable keyboard port - whenever there is new data
> starts coming from the port serio core will try to find proper driver
> for it. I wonder why this is not working on boxes in question.
The DRAC3 doesn't respond to ANY commands, thus the atkbd probe fails.
--
Vojtech Pavlik
Director SuSE Labs
next prev parent reply other threads:[~2006-02-21 21:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 20:43 Suppressing softrepeat 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
2006-02-22 21:16 ` Pete Zaitcev
2006-02-21 21:15 ` Dmitry Torokhov
2006-02-21 21:35 ` Vojtech Pavlik [this message]
-- strict thread matches above, loose matches on Subject: below --
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=20060221213525.GA12526@suse.cz \
--to=vojtech@suse.cz \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stuart_hayes@dell.com \
--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