From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: "Andrew Morton" <akpm@osdl.org>,
"Linux Fbdev development list"
<linux-fbdev-devel@lists.sourceforge.net>,
"Linux Kernel Development" <linux-kernel@vger.kernel.org>,
"Greg KH" <greg@kroah.com>
Subject: Re: [PATCH 5/5] VT binding: Add new doc file describing the feature
Date: Sat, 10 Jun 2006 21:05:05 -0400 [thread overview]
Message-ID: <9e4733910606101805t3060c0cdgd08ceabe8cfe4e0e@mail.gmail.com> (raw)
In-Reply-To: <9e4733910606101749r77d72a56mbcf6fb3505eb1de0@mail.gmail.com>
On 6/10/06, Jon Smirl <jonsmirl@gmail.com> 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?
The kernel is also missing the logic for controlling which VGA card is
active when multiple ones exist in the same box.
> 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.
When I say dropped, I mean drop the feature of having multiple drivers
simultaneously open by the VT layer. You would still be able to switch
from vgacon to fbcon by using sysfs. You just wouldn't be able to use
VT swap hotkeys between them.
> 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.
>
> --
> Jon Smirl
> jonsmirl@gmail.com
>
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2006-06-11 1:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 8:40 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 [this message]
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 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2006-06-11 1:16 ` Antonino A. Daplas
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 1:27 ` Bernd Eckenfels
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=9e4733910606101805t3060c0cdgd08ceabe8cfe4e0e@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=adaplas@gmail.com \
--cc=akpm@osdl.org \
--cc=greg@kroah.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
all inboxes | Powered by JetHome®