From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Greg KH <greg@kroah.com>
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: Sat, 21 Feb 2004 11:16:47 +1100 [thread overview]
Message-ID: <1077322606.10864.1.camel@gaston> (raw)
In-Reply-To: <20040220235410.GB17771@kroah.com>
On Sat, 2004-02-21 at 10:54, Greg KH wrote:
> What's wrong with the current range of init call sections? Can't that
> work for fb devices today?
We can probably work with those. I just don't fell like changing that
part of fbdev right now. More important fixes to get in first (and
there's a shitload of crap related to calling the setup functions in
fbdev's that need fixing too if/when we change that init stuff).
My idea about adding an initcall level was for pure convenience, but
may be wrong. It's handy to have the console inited before the rest
that's all ;) We can leave that out for now, maybe just linking
drivers/video before the rest is enough to get that anyway.
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
prev parent reply other threads:[~2004-02-21 0:28 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
2004-02-21 0:16 ` Benjamin Herrenschmidt [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=1077322606.10864.1.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=greg@kroah.com \
--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).