From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Helge Hafting <helge.hafting@hist.no>
Cc: Jon Smirl <jonsmirl@yahoo.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: OLS and console rearchitecture
Date: Thu, 05 Aug 2004 21:32:09 +0100 [thread overview]
Message-ID: <1091737928.8366.6.camel@localhost.localdomain> (raw)
In-Reply-To: <4111F624.7080605@hist.no>
On Iau, 2004-08-05 at 09:56, Helge Hafting wrote:
> Isn't the "unique VGA" a disappearing problem?
Alas not.
> Please avoid unnecessary disabling of such devices, that only causes
> trouble for those of use trying to use several screens at once. (Possibly
> with several simultaneous _users_, who don't want their screen disabled
> for no
> good reason.) Of course one may have to buy the "right" cards when
> setting up
> such a machine.
The goal is to have a control device to arbitrate it. This doesn't
generally cause a performance hit and X currently handles it internally
using RAC but once you have multiple uses of VGA space the arbitration
has to go kernel side
next prev parent reply other threads:[~2004-08-05 21:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 14:24 OLS and console rearchitecture Jon Smirl
2004-08-02 14:54 ` Alexander E. Patrakov
2004-08-02 16:07 ` Miquel van Smoorenburg
2004-08-02 16:21 ` Andreas Schwab
2004-08-02 17:40 ` Alan Cox
2004-08-03 8:44 ` Andreas Schwab
2004-08-02 16:16 ` Jon Smirl
2004-08-05 11:08 ` Martin Waitz
2004-08-02 18:33 ` Jesse Barnes
2004-08-03 0:01 ` Benjamin Herrenschmidt
2004-08-05 8:56 ` Helge Hafting
2004-08-05 20:32 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-29 0:44 [Linux-fbdev-devel] " Ian Romanick
2004-07-29 1:19 ` Jon Smirl
2004-07-29 8:34 ` Geert Uytterhoeven
2004-07-28 18:53 Jon Smirl
2004-07-28 20:10 ` Alan Cox
2004-07-28 21:31 ` Kronos
2004-07-28 22:57 ` [Linux-fbdev-devel] " Alan Cox
2004-07-30 22:19 ` Kronos
2004-07-30 23:31 ` Jon Smirl
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=1091737928.8366.6.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=helge.hafting@hist.no \
--cc=jonsmirl@yahoo.com \
--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 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.