From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: "Pete Zaitcev" <zaitcev@redhat.com>
Cc: linux-kernel@vger.kernel.org, vojtech@suse.cz, stuart_hayes@dell.com
Subject: Re: Suppressing softrepeat
Date: Tue, 21 Feb 2006 16:15:57 -0500 [thread overview]
Message-ID: <d120d5000602211315y60ad2861n4cd64535f9f4850d@mail.gmail.com> (raw)
In-Reply-To: <20060221124308.5efd4889.zaitcev@redhat.com>
On 2/21/06, Pete Zaitcev <zaitcev@redhat.com> wrote:
> Hi, Dmitry,
>
Hi Pete,
> Dell people passed on a request to add a new parameter, "nosoftrepeat",
> to i8042 (in atkbd.c). So, if I understand right, things should work so:
>
> - None set in grub.conf: Softrepeat is set by the driver as detected
> or derived. This is the default.
> - "softrepeat" set: Softrepeat is on, regardless
> - "nosoftrepeat" set: Softrepeat is off, regardless
> - Both "softrepeat" and "nosoftrepeat" are set: Do not do that.
>
> The code looked confusing, but there is an good explanation in this bug:
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=181457
>
> In short words, DRAC3 "plugs into" the keyboard connector, but does not
> emulate output, so we detect this as "dumb" keyboard and enable softrepeat.
> But softrepeat causes double keypresses.
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
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.
--
Dmitry
next prev parent reply other threads:[~2006-02-21 21:16 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
2006-02-22 21:16 ` Pete Zaitcev
2006-02-21 21:15 ` Dmitry Torokhov [this message]
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=d120d5000602211315y60ad2861n4cd64535f9f4850d@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®