linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@pol.net>
To: jsimmons@pentafluge.infradead.org
Cc: adaplas@pol.net, akpm@osdl.org, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Re: [PATCH 1/4][RESEND][FBDEV]: Core fbcon fixes
Date: Thu, 24 Jun 2004 09:11:05 +0800 (PHT)	[thread overview]
Message-ID: <61276.10.250.10.1.1088039465.squirrel@sq03.pol.net> (raw)
In-Reply-To: <Pine.LNX.4.56.0406240112270.609@pentafluge.infradead.org>

>
> Wow. That is a big patch. I will loook it over. I had some ideas I like

It is a big patch.

Needed because fb_console_init and set_con2fbmap are just plain broken. 
Really, you need to adjust module reference counts, re/deinitialize the
cursor timer, initialize/reinitialize the global arrays, preserve user
fonts, consider that you can have multiple fbdevs mapped to different
consoles, consider that you can load/unload fbdev modules at will, etc.
All the above complexities were introduced because fbdev was separated
from fbcon.  Not doing/taking note of any of the above is just asking for
trouble. (The 2.4 framework is simpler because fbcon is automatically
initialized with fbdev).

Plus, the patch also combined the changes needed to prevent screen
corruption at boot time.  Note that the logo code is actually simplified
by the changes.

> to  try myslef. I like to have you be able to map the fbdevs to teh
> correct  VCs at boot time. If one is modular as soon as you load that
> module it  maps to fbcon automatically :-) Like in 2.4.X.
>

Setcon2fbmap is already fixed so you can use it to choose which
framebuffers to load.

Choosing which fbdev to map to a console at boot time is as simple as
adding a boot parameter and use that in fb_console_init.

As for the 2.4 behavior of automatically initializing fbcon when an fb
module is loaded, that is also simple.  Add another notifier event which
is called during register_framebuffer that will subsequently call
fb_console_init().

However you implement it, with this patch, the framework is already in place.

Tony





-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com

      reply	other threads:[~2004-06-24  1:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-21 22:39 [PATCH 1/3] [FBDEV]: Core fbcon fixes Antonino A. Daplas
2004-06-22 13:20 ` Antonino A. Daplas
2004-06-23 15:59 ` Benjamin Herrenschmidt
2004-06-24  0:14 ` [PATCH 1/4][RESEND][FBDEV]: " jsimmons
2004-06-24  1:11   ` Antonino A. Daplas [this message]

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=61276.10.250.10.1.1088039465.squirrel@sq03.pol.net \
    --to=adaplas@pol.net \
    --cc=akpm@osdl.org \
    --cc=jsimmons@pentafluge.infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).