From: Helge Hafting <helgehaf@aitel.hist.no>
To: Boszormenyi Zoltan <zboszor@freemail.hu>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Multiple keyboard/monitor vs linux-2.6?
Date: Sat, 13 Dec 2003 14:14:05 +0100 [thread overview]
Message-ID: <20031213131405.GA11073@hh.idb.hist.no> (raw)
In-Reply-To: <20031212214310.GA744@node1.opengeometry.net>
On Fri, Dec 12, 2003 at 04:43:10PM -0500, William Park wrote:
> On Fri, Dec 12, 2003 at 09:13:28AM +0000, Boszormenyi Zoltan wrote:
> >
> > 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.
>
> Does it work?
>
It works with 2.6.0-test11. Prepare a kernel source tree,
check out ruby from cvs, copy the ruby-2.6 parts into
the kernel tree.
I run my home machine this way:
2 standard keyboards, one connected to the keyboard port and
another connected to the ps2 mouse port.
2 mice, both connected to serial ports.
2 screens, connected to the two outputs of a matrox G550.
One xserver runs using standard mga driver, another xserver
uses the unaccelerated framebuffer driver on the framebuffer
displayed on the second screen.
The screen with the accelerated server also have accelerated opengl.
The other screen uses software opengl, fast enough for
frozen-bubble and rocks&diamonds, but not for tuxracer.
xdm manages both screens, so any user can log in at either screen.
The G550 isn't ideal for this, because resetting the accelerated xserver
causes the framebuffer screen to blink (accelerated xserver
disturbs the other display while setting resolution.)
This is a software problem though.
It seems possible to run accelerated servers at both screens as
long as only one uses opengl. I haven't bothered yet because
unaccelerated 2D performance seems fine for all purposes with
dual 333MHz processors.
Using two video cards AGP+PCI or PCI+PCI solves the interactions between
the two displays, but then you need a modified xserver. (Std.
Xserver turns off video cards it donesn't use, without worrying
about other servers using the other card.)
Letting two servers use a single card don't have this problem,
but it could possibly have other problems.
Helge Hafting
next prev parent reply other threads:[~2003-12-13 13:03 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 ` William Park
2003-12-13 13:14 ` Helge Hafting [this message]
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 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=20031213131405.GA11073@hh.idb.hist.no \
--to=helgehaf@aitel.hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=zboszor@freemail.hu \
/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
all inboxes | Powered by JetHome®