All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Jon Smirl <jonsmirl@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>
Subject: Re: [PATCH 0/7] Detaching fbcon
Date: Wed, 07 Jun 2006 03:45:48 +0800	[thread overview]
Message-ID: <4485DB6C.704@gmail.com> (raw)
In-Reply-To: <9e4733910606060919p2a137e07wd58b51a227f5aa5e@mail.gmail.com>

Jon Smirl wrote:
> On 6/6/06, Jon Smirl <jonsmirl@gmail.com> wrote:
>> On 6/6/06, Antonino A. Daplas <adaplas@gmail.com> wrote:
>> > Overall, this feature is a great help for developers working in the
>> > framebuffer or console layer.  There is not need to continually
>> reboot the
>> > kernel for every small change. It is also useful for regular users
>> who wants
>> > to choose between a graphical console or a text console without
>> having to
>> > reboot.
>>
>> Instead of the sysfs attribute, what about creating a new escape
>> sequence that you send to the console system to detach? Doing it that
>> way would make more sense from a stacking order. It just seems
>> backwards to me that you ask a lower layer to detach from the layer
>> above it. The escape sequence would also work for any console
>> implementation, not just fbcon.
>>
>> If console detached this way and there was nothing to fallback to
>> (systems without VGAcon), it would know not to try and print anything
>> until something reattaches to it.
> 
> Another thought, controlling whether console is attached or not is an
> attribute of console, not of fbcon.

If the console attached fbcon, then I agree that console should decide
when to detach fbcon.  But that's not what happens, it's fbcon that
attaches itself.

It's not that you're wrong, it's just how the current vt/console layer
works.  If someone do decide to add this feature to the vt/console layer,
then I'm more than willing to have fbcon support that as well.
  
Tony

  reply	other threads:[~2006-06-06 19:45 UTC|newest]

Thread overview: 29+ 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 [this message]
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
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 13:25   ` [Linux-fbdev-devel] " Knut Petersen
2006-06-11 20:57   ` Antonino A. Daplas
2006-06-11 20:57     ` [Linux-fbdev-devel] " Antonino A. Daplas
2006-06-12  7:49     ` Knut Petersen
2006-06-12  7:49       ` [Linux-fbdev-devel] " Knut Petersen
2006-06-12 12:17       ` Antonino A. Daplas
2006-06-12 12:17         ` [Linux-fbdev-devel] " Antonino A. Daplas
2006-06-12 12:25         ` Geert Uytterhoeven
2006-06-12 12:25           ` [Linux-fbdev-devel] " Geert Uytterhoeven
2006-06-12 13:28         ` Michal Suchanek
2006-06-12 14:15           ` [Linux-fbdev-devel] " Antonino A. Daplas
2006-06-12 14:15             ` Antonino A. Daplas
2006-06-12 16:44             ` Michal Suchanek
2006-06-12 14:20           ` [Linux-fbdev-devel] " Michel Dänzer
2006-06-12 14:20             ` Michel Dänzer
2006-06-12 16:46             ` Michal Suchanek
2006-06-12 17:20               ` Michel Dänzer
2006-06-12 17:20                 ` [Linux-fbdev-devel] " 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=4485DB6C.704@gmail.com \
    --to=adaplas@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 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.