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: Dave Airlie <airlied@gmail.com>, Andrew Morton <akpm@osdl.org>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/7] Detaching fbcon
Date: Wed, 07 Jun 2006 07:15:56 +0800	[thread overview]
Message-ID: <44860CAC.90107@gmail.com> (raw)
In-Reply-To: <9e4733910606061455l2ab3a217q431a90a6c3555813@mail.gmail.com>

Jon Smirl wrote:
> On 6/6/06, Dave Airlie <airlied@gmail.com> wrote:
>> > > >
>> > How is the stack maintained of what was previously bound to console?
>> > What if I unbind fbcon on a system that doesn't have VGAcon for a
>> backup?
>>
>> You could try actually reading the patches...
> 
> I was working on a patch for this but now I've lost interest.

How come? I never believed you're the type to lose interest so easily :-)

> 
> Detach should be an attribute off from /dev/console. /dev/console is
> using the standard device support and appears at
> /sys/class/tty/console so /sys/class/tty/console/detach can be added
> as an attribute. /sys/class/tty/console could have another attribute
> which lists the available drivers. One solution would be for the
> attribute to list the names of the available drivers that have
> registered with console and then copy one of those names back to the
> attribute to select where console is bound.
> 
> In my opinion attach/detach does not belong as an attribute on fbcon,
> it is part of /dev/console. The fact that fbcon has to ask console to
> unbind from it implies these attributes are in the wrong place.

Okay, you and Andrew persuaded me to change the location of the control.
I did say that if someone makes the necessary change to the vt layer that
it won't be a problem. The necessary infrastructure is already introduced
by this patch to make it work like what you and Andrew want. 

Tony
 

  reply	other threads:[~2006-06-06 23:15 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-06 11:08 [PATCH 0/7] Detaching fbcon Antonino A. Daplas
2006-06-06 16:10 ` Jon Smirl
2006-06-06 16:19   ` Jon Smirl
2006-06-06 19:45     ` Antonino A. Daplas
2006-06-06 21:00       ` Jon Smirl
2006-06-06 21:39         ` Dave Airlie
2006-06-06 21:55           ` Jon Smirl
2006-06-06 23:15             ` Antonino A. Daplas [this message]
2006-06-06 23:17         ` Antonino A. Daplas
2006-06-06 19:45   ` Antonino A. Daplas
2006-06-11 13:25 ` Knut Petersen
2006-06-11 20:57   ` Antonino A. Daplas
2006-06-12  7:49     ` Knut Petersen
2006-06-12 12:17       ` Antonino A. Daplas
2006-06-12 12:25         ` Geert Uytterhoeven
2006-06-12 13:28         ` Michal Suchanek
2006-06-12 14:15           ` [Linux-fbdev-devel] " Antonino A. Daplas
2006-06-12 16:44             ` Michal Suchanek
2006-06-12 14:20           ` [Linux-fbdev-devel] " Michel Dänzer
2006-06-12 16:46             ` Michal Suchanek
2006-06-12 17:20               ` Michel Dänzer

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=44860CAC.90107@gmail.com \
    --to=adaplas@gmail.com \
    --cc=airlied@gmail.com \
    --cc=akpm@osdl.org \
    --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).