From: Vojtech Pavlik <vojtech@suse.cz>
To: Pavel Roskin <proski@gnu.org>
Cc: James Simmons <jsimmons@transvirtual.com>, linux-kernel@vger.kernel.org
Subject: Re: AT keyboard optional on i386?
Date: Tue, 29 May 2001 10:00:34 +0200 [thread overview]
Message-ID: <20010529100034.A911@suse.cz> (raw)
In-Reply-To: <Pine.LNX.4.10.10105282027030.3783-100000@transvirtual.com> <Pine.LNX.4.33.0105290021420.12495-100000@portland.hansa.lan>
In-Reply-To: <Pine.LNX.4.33.0105290021420.12495-100000@portland.hansa.lan>; from proski@gnu.org on Tue, May 29, 2001 at 12:50:59AM -0400
On Tue, May 29, 2001 at 12:50:59AM -0400, Pavel Roskin wrote:
> Hi, James!
>
> > So as you can see even USB keyboards depend on pc_keyb.c. So their is
> > no way around this.
>
> Perhaps redefining kbd_read_input() will help. It's cruel, I know :-)
Or just kill allocating the IRQ in the pc_keyb.c file. It worked for me.
> > You can a few nice tricks with it like plug in two PS/2 keyboards. I
> > have this for my home setup. The only thing is make sure you don't
> > have both keyboards plugged in when you turn your PC on. I found BIOS
> > get confused by two PS/2 keyboards. As you can it is very easy to
> > multiplex many keyboards with the above design. I have had 4 different
> > keyboards hooked up to my system and functioning at the same time. We
> > even got a Sun keyboard to work on a intel box :-)
>
> That's what we like Linux for. It doesn't get confused when everything
> else does :-)
>
> Thanks for your very interesting reply.
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2001-05-29 8:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-26 0:21 AT keyboard optional on i386? Pavel Roskin
2001-05-29 4:11 ` James Simmons
2001-05-29 4:50 ` Pavel Roskin
2001-05-29 8:00 ` Vojtech Pavlik [this message]
2001-05-31 22:52 ` Ricky Beam
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=20010529100034.A911@suse.cz \
--to=vojtech@suse.cz \
--cc=jsimmons@transvirtual.com \
--cc=linux-kernel@vger.kernel.org \
--cc=proski@gnu.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