From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>, Greg KH <greg@kroah.com>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 5/5] VT binding: Add new doc file describing the feature
Date: Sun, 11 Jun 2006 09:16:03 +0800 [thread overview]
Message-ID: <448B6ED3.5060408@gmail.com> (raw)
In-Reply-To: <9e4733910606101749r77d72a56mbcf6fb3505eb1de0@mail.gmail.com>
Jon Smirl wrote:
> On 6/10/06, Antonino A. Daplas <adaplas@gmail.com> wrote:
>> > I see now that you can have tty0-7 assigned to a different console
>> > driver than tty8-63.
>> > Why do I want to do this?
>>
>> Multi-head. I can have vgacon on the primary card for tty0-7,
>> fbcon on the secondary card for tty8-16.
>
> That's what I thought, I couldn't see any other reason. The kernel
> doesn't support input from multiple users so multihead can only be
> used by a single user.
>
> Does anyone use single user multihead on current systems? The kernel
> doesn't have code in it to initialize secondary VGA cards. What modern
> non-VGA hardware does this work on?
matroxfb supports multihead and fbcon already has this feature for a
long time, ie you can bind /dev/fb0 to tty0-3 and /dev/fb1 to tty4-6.
And there are definite users because I happen to break this feature once
and I got rained with complaints :-)
>
> If this feature doesn't work on current hardware, could it be dropped?
> It would make binding to the vt system much simpler if only one driver
> could be bound at a time. Anything we do to make that system simpler
> would benefit everyone.
You can't drop something that's already in the kernel and has users, well,
the binding part at least. What we don't currently have is the fine-grained
control and because of the reason's you mentioned, I said that it's for the
future.
(Note1: fbcon already has support to selectively bind/unbind drivers
to specific tty's, using the con2fbmap utility.)
So what we have is control for wholescale binding and unbinding of
drivers, which essentially results in only 1 driver loaded at one time.
(Note2: fbcon already has an option to determine what range of vc's to
control, as a kernel boot parameter, so we can't just drop something
that's already supported by one driver at least. Though I know of no one,
including myself, who uses this feature.)
>
> At some future point I would like to explore pushing the VT system out
> to user space where it becomes much easier to make it multi-user and
> multi-head. If you do that, something like a single user, in-kernel
> system management console makes more sense.
Yes.
Tony
next prev parent reply other threads:[~2006-06-11 1:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 8:40 [PATCH 5/5] VT binding: Add new doc file describing the feature Antonino A. Daplas
2006-06-10 5:53 ` Jon Smirl
2006-06-10 13:27 ` Antonino A. Daplas
2006-06-10 16:16 ` Jon Smirl
2006-06-10 17:01 ` Jon Smirl
2006-06-10 17:22 ` Jon Smirl
2006-06-10 21:26 ` Antonino A. Daplas
2006-06-10 23:44 ` Jon Smirl
2006-06-11 0:21 ` Antonino A. Daplas
2006-06-11 0:49 ` Jon Smirl
2006-06-11 1:05 ` Jon Smirl
2006-06-11 1:44 ` Antonino A. Daplas
2006-06-11 2:26 ` Jon Smirl
2006-06-11 3:05 ` Antonino A. Daplas
2006-06-12 8:31 ` Geert Uytterhoeven
2006-06-11 1:16 ` Antonino A. Daplas [this message]
2006-06-11 2:05 ` Jon Smirl
2006-06-11 3:03 ` Antonino A. Daplas
2006-06-11 3:27 ` Jon Smirl
2006-06-11 4:36 ` Antonino A. Daplas
2006-06-11 4:46 ` Antonino A. Daplas
2006-06-11 20:59 ` Jon Smirl
2006-06-11 22:04 ` Antonino A. Daplas
2006-06-11 3:09 ` Randy.Dunlap
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=448B6ED3.5060408@gmail.com \
--to=adaplas@gmail.com \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=jonsmirl@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--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;
as well as URLs for NNTP newsgroup(s).