From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: James Simmons <jsimmons@infradead.org>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: fb_console_init fix.
Date: Sat, 21 Feb 2004 09:56:56 +1100 [thread overview]
Message-ID: <1077317816.9623.20.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.44.0402202156340.6798-100000@phoenix.infradead.org>
On Sat, 2004-02-21 at 08:58, James Simmons wrote:
> Hi!
>
> This patch fixes fb_console_init from being called twice. I still need
> to fix set_con2fb but this helps but this is still important to get in.
I hate those #ifdef MODULE. They are plaguing the drivers too, because
of our crazy initialization scheme...
(Linus: that patch should still go in, doing better is probably a
2.7 target in this case).
If we want the fb stuff to be initialized before other drivers, we
probably want to create an init step before devices and after PCI
probe, but is that really necessary ?
The core fbdev should just need a subsys initcall. fbcon could use
that too and register a notifier. Then we could use the notifier
mecanism to notify fbcon when fbdev's are added (from
register_framebuffer) and get rid of all of the init crap
The only remaining junk is to deal with the setup= stuff, but
then, it could be done by having the drivers provide their
"name" string & setup function in the ops structure passed
on register, and have us call back the driver straight away,
though that's a big change of the way drivers are initialized.
Or we could add an fb_check_setup("name", my_driver_setup) call
to be done by the drivers before register_framebuffer is called
Ben
.
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
next prev parent reply other threads:[~2004-02-20 23:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-20 21:58 fb_console_init fix James Simmons
2004-02-20 22:56 ` Benjamin Herrenschmidt [this message]
2004-02-20 23:54 ` Greg KH
2004-02-21 0:16 ` Benjamin Herrenschmidt
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=1077317816.9623.20.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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).