From: "Svetoslav Slavtchev" <svetljo@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Multiple keyboard/monitor vs linux-2.6?
Date: Fri, 12 Dec 2003 11:03:57 +0100 (MET) [thread overview]
Message-ID: <1622.1071223437@www41.gmx.net> (raw)
Hi,
zb == Zoltán Böszörményi
< zb >
is there a way to assign different keyboards to different vcs?
I would like to set up a machine that has 2 keyboards, 2 mice and
2 videocards and run XFree-4.x on both heads. The videocard/monitor and
mouse settings are easy to set up but I cannot find a device setting
for the keyboard in man XF86Config. How can I do it with mainline kernels?
</ zb >
you can not do it with mainline kernel
you need both patched kernel and XFree, although the
second might be skiped in case a similar functionality
added by the kernel patch is used
< zb >
After some googleing I found something called "backstreet ruby"
http://startx.times.lv/eng-faq.html
</ zb >
check the entire documentation there
and visit the links section -> you'll get the big picture
for 2.6 most info is still on the linuxconsole ml archive
< zb >
This gave me this info (howto in a nutshell):
1. Boot with kernel option "dumbcon=N" to activate N dummy console.
</ zb >
mostly undocumented, but dumbcon= ... is not obligatory for 2.6,
you can also use multiple independent framebuffer consoles instead,
which is still work in progress
< zb >
2. cat /proc/bus/input/devices gives the input devices, search for keyboard
entries.
3. To assign a keyboard to a VT, feed the keyboard Phys= entry into
a VT, e.g. echo "isa0060/serio0/input0" > /proc/bus/console/00/keyboard
4. Start the X server on the proper VT.
</ zb >
you can configure hotplug to do this for you
and let a display manager start X for you,
but i'm not sure how well will this work with
multiple framebuffer consoles
< zb >
The functionality can be found at linuxconsole.sourceforge.net.
Will this be included into mainline near term? Say 2.6.[12]?
The ruby-2.6 is against 2.6.0-test9 so it's almost uptodate.
</ zb >
the ruby tree works with current 2.6 too
multiple framebuffer console is not yet polished
and the framebuffer drivers in vanilla 2.6 aren't
in very good shape too
i really doubt it will be included in the near term,
i think it will be first merged in 2.7
(hopefully right after it opens) and then it will
be "backported" to 2.6, may be arround 2.6.1[0-9]
best,
svetljo
--
+++ GMX - die erste Adresse für Mail, Message, More +++
Neu: Preissenkung für MMS und FreeMMS! http://www.gmx.net
next reply other threads:[~2003-12-12 10:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-12 10:03 Svetoslav Slavtchev [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-12 22:27 Multiple keyboard/monitor vs linux-2.6? 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
[not found] <fa.da53dsa.dho216@ifi.uio.no>
2003-12-12 21:43 ` William Park
2003-12-13 13:14 ` Helge Hafting
2003-12-13 21:12 ` William Park
2003-12-15 12:18 ` Helge Hafting
2003-12-15 20:38 ` William Park
2003-12-15 17:18 ` Pavel Machek
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=1622.1071223437@www41.gmx.net \
--to=svetljo@gmx.de \
--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