From: Helge Hafting <helgehaf@aitel.hist.no>
To: William Park <opengeometry@yahoo.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Multiple keyboard/monitor vs linux-2.6?
Date: Mon, 15 Dec 2003 13:18:14 +0100 [thread overview]
Message-ID: <3FDDA686.6030502@aitel.hist.no> (raw)
In-Reply-To: <20031213211234.GB448@node1.opengeometry.net>
William Park wrote:
> On Sat, Dec 13, 2003 at 02:14:05PM +0100, Helge Hafting wrote:
[...]
>>I run my home machine this way:
>>2 standard keyboards, one connected to the keyboard port and
>>another connected to the ps2 mouse port.
>
>
> Plug PS/2 keyboard into PS/2 mouse port??? I didn't know you can do
> that.
The two ports are the same hardware, which makes sense as they
serve the same purpose - serial communication with a slow device.
The common case is one keyboard and one mouse, but two mice
or two keyboards works just as well as long as the software
expects it. Linux 2.6 have no problems with this.
You need the ruby patch to use the two keyboards independently,
the standard kernel merges input from all attached keyboards into
one console.
You may attach a lot more keyboards using usb keyboards.
Helge Hafting
next prev parent reply other threads:[~2003-12-15 12:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.da53dsa.dho216@ifi.uio.no>
2003-12-12 21:43 ` Multiple keyboard/monitor vs linux-2.6? William Park
2003-12-13 13:14 ` Helge Hafting
2003-12-13 21:12 ` William Park
2003-12-15 12:18 ` Helge Hafting [this message]
2003-12-15 20:38 ` William Park
2003-12-15 17:18 ` Pavel Machek
2003-12-12 22:27 Svetoslav Slavtchev
2003-12-12 22:45 ` William Park
2003-12-12 23:09 ` Svetoslav Slavtchev
2003-12-12 23:46 ` William Park
2003-12-13 1:05 ` Svetoslav Slavtchev
2003-12-13 10:20 ` John Bradford
2003-12-13 10:28 ` Svetoslav Slavtchev
-- strict thread matches above, loose matches on Subject: below --
2003-12-12 10:03 Svetoslav Slavtchev
2003-12-12 9:12 Boszormenyi Zoltan
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=3FDDA686.6030502@aitel.hist.no \
--to=helgehaf@aitel.hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=opengeometry@yahoo.ca \
/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