From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Sergey Tursanov <__gsr@mail.ru>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Re[2]: PC keyboard rate/delay
Date: Tue, 12 Jun 2001 19:23:51 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.05.10106121920100.7169-100000@callisto.of.borg> (raw)
In-Reply-To: <53176576.20010612212337@mail.ru>
On Tue, 12 Jun 2001, Sergey Tursanov wrote:
> AC> You must have been reading my mind. Yesterday I traced at least one X11
> AC> hang down to the kernel and X server both frobbing with the port at the same
> AC> time and crashing the microcontroller on my PC110.
>
> I think it would be better to place all of kbd controller code
> into the kernel instead of using various userspace programs
> such as kbdrate. Otherwise why KDKBDREP was defined ?-)
Because (almost?) all m68k machines don't have PC style keyboard controllers,
so we _had_ to invent some other way to implement it in a portable (across all
m68k machines) way.
<wishful thinking>
Of course it would be nice if all architectures would want to use it.
</wishful thinking>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2001-06-12 17:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-12 14:19 PC keyboard rate/delay Sergey Tursanov
2001-06-12 16:02 ` Alan Cox
2001-06-12 16:21 ` James Simmons
2001-06-12 17:23 ` Re[2]: " Sergey Tursanov
2001-06-12 17:23 ` Geert Uytterhoeven [this message]
2001-06-12 17:56 ` James Simmons
2001-06-13 5:31 ` Geert Uytterhoeven
2001-06-14 17:57 ` Alan Cox
2001-06-12 20:19 ` Guest section DW
2001-06-12 20:10 ` Guest section DW
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=Pine.LNX.4.05.10106121920100.7169-100000@callisto.of.borg \
--to=geert@linux-m68k.org \
--cc=__gsr@mail.ru \
--cc=alan@lxorguk.ukuu.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).