From: Pete Zaitcev <zaitcev@redhat.com>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: dtor_core@ameritech.net, linux-kernel@vger.kernel.org,
stuart_hayes@dell.com, zaitcev@redhat.com
Subject: Re: Suppressing softrepeat
Date: Wed, 22 Feb 2006 12:00:47 -0800 [thread overview]
Message-ID: <20060222120047.4fd9051e.zaitcev@redhat.com> (raw)
In-Reply-To: <20060221210800.GA12102@suse.cz>
On Tue, 21 Feb 2006 22:08:00 +0100, Vojtech Pavlik <vojtech@suse.cz> wrote:
> A much simpler workaround for the DRAC3 is to set the softrepeat delay
> to at least 750ms, using kbdrate(8), which will call the proper console
> ioctl, resulting in updating the softrepeat parameters.
>
> I prefer workarounds for problematic hardware done outside the kernel,
> if possible.
I agree with the sentiment when posed in the abstract way, but let me
tell you why this case is different.
Firstly, there's nothing "problematic" about this. It's just how it is.
The only problematic thing here is our code. Currently, the situation is
assymetric. It is possible to force softrepeat on, but not possible to
force softrepeat off. Isn't it broken?
Secondly, 750ms may be not enough. Stuart is being shy here and posting
explanations to Bugzilla for some reason.
Lastly, it's such a PITA to add these things into the userland, that
it's completely impractical. Console is needed the most when things go
wrong. In such case, that echo(1) may not be reached before the single
user shell. And stuffing it into the initrd is for Linux weenies only,
unless automated by mkinitrd.
I think you're being unreasonable here. I am not asking for NFS root
or IP autoconfiguration and sort of complicated process which ought to
be done in userland indeed.
-- Pete
next prev parent reply other threads:[~2006-02-22 20:01 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 [this message]
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
-- 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=20060222120047.4fd9051e.zaitcev@redhat.com \
--to=zaitcev@redhat.com \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stuart_hayes@dell.com \
--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