From: Greg KH <greg@kroah.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: James Simmons <jsimmons@infradead.org>,
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: Fri, 20 Feb 2004 15:54:12 -0800 [thread overview]
Message-ID: <20040220235410.GB17771@kroah.com> (raw)
In-Reply-To: <1077317816.9623.20.camel@gaston>
On Sat, Feb 21, 2004 at 09:56:56AM +1100, Benjamin Herrenschmidt wrote:
>
> 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
What's wrong with the current range of init call sections? Can't that
work for fb devices today?
thanks,
greg k-h
-------------------------------------------------------
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-21 0:03 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
2004-02-20 23:54 ` Greg KH [this message]
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=20040220235410.GB17771@kroah.com \
--to=greg@kroah.com \
--cc=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).