From: Wakko Warner <wakko@animx.eu.org>
To: Simon Hay <simon@haywired.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Multiple monitors
Date: Mon, 3 Sep 2001 16:49:53 -0400 [thread overview]
Message-ID: <20010903164953.A3243@animx.eu.org> (raw)
In-Reply-To: <20010903214829.B17488@unthought.net> <Pine.LNX.4.33.0109032107280.2297-100000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.33.0109032107280.2297-100000@localhost.localdomain>; from Simon Hay on Mon, Sep 03, 2001 at 09:11:24PM +0100
> > XFree86 has pretty good support for multiple heads.
> >
> > If you tie an xterm to the root window, I guess you would get something
> > pretty close to what you're looking for. Or, configure some window manager
> > properly to do exactly what you want.
> >
>
> I had considered doing that - I believe that some of the framebuffer
> code supports multiple heads as well(?) - but in this particular case it
> wasn't appropriate - the whole point was to demonstrate what could be
> achieved using only a command line ;-) Also, though, on dedicated servers
> etc. I'd rather not be running X if I didn't have to. Would this be a
> particularly difficult thing to implement as a kernel patch? I'd like to
> try to get involved in kernel development at some point and am looking for
> something to ease myself in slowly - preferably something useful but
> unimportant ;-) Are there any show stoppers involved here - or does
> anyone have any other ideas?
I thought of doing something like this but using a matrox g400 or g450 dual
head card. primary would be for X, secondary would be a console. Not sure
if that's more difficult or not. Something I'd like to have, however.
--
Lab tests show that use of micro$oft causes cancer in lab animals
next prev parent reply other threads:[~2001-09-03 20:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-03 18:44 Multiple monitors Simon Hay
2001-09-03 19:48 ` Jakob Østergaard
2001-09-03 20:11 ` Simon Hay
2001-09-03 20:49 ` Wakko Warner [this message]
2001-09-03 20:42 ` Simon Hay
2001-09-03 20:52 ` Jan Kasprzak
2001-09-04 16:52 ` James Simmons
2001-09-07 0:55 ` Jamie Lokier
2001-09-10 22:58 ` Pavel Machek
2001-09-13 12:51 ` Jamie Lokier
2001-09-03 20:57 ` Matan Ziv-Av
2001-09-04 7:56 ` Ghozlane Toumi
2001-09-04 16:44 ` James Simmons
2001-09-05 18:01 ` sacx
2001-09-05 18:13 ` sacx
-- strict thread matches above, loose matches on Subject: below --
2011-06-01 14:15 Alexandr Klimenko
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=20010903164953.A3243@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=simon@haywired.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.