linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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:44:52 +0800	[thread overview]
Message-ID: <448B7594.6040408@gmail.com> (raw)
In-Reply-To: <9e4733910606101805t3060c0cdgd08ceabe8cfe4e0e@mail.gmail.com>

Jon Smirl wrote:
> 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.
>>
> 
> 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.

Quoting you:

"Googling around the only example I could find was someone with a VGA
card and a Hercules card. They setup 8 consoles on each card."

How do you think they accomplished that? They did not rewrite the VT
layer, all they need to do is change the 'first' and 'last' parameter
passed to take_over_console() in mdacon.c.  This implies that the VT
layer already supports multiple active VT console drivers, maybe as
early as 2.2, and no, we won't remove that.

Tony 

  reply	other threads:[~2006-06-11  1:45 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 [this message]
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
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=448B7594.6040408@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).