From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Paul Mundt <lethal@linux-sh.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
James Simmons <jsimmons@infradead.org>
Subject: Re: Re: [PATCH] kyrofb support
Date: Wed, 14 Jan 2004 15:58:49 +1100 [thread overview]
Message-ID: <1074056156.765.23.camel@gaston> (raw)
In-Reply-To: <20040113180926.5fdb0824.akpm@osdl.org>
> In general, what are the fbdev drivers doing here btw? It's very strange
> that some core file (fbmem.c) has to "know" about individual card drivers.
> It should be sufficient for the driver to just register itself with the core
> at the drivers's module_init() time.
>
> Sigh. Too late to fix that now I guess.
Pre-historical junk that should be killed for 2.7 (I hope).
There isn't that a bad internal API change, the main of it is the allocation
and freeing of the fbdev, adapting the driver to that should be trivial. I
hope James will feed you with the new stuff asap now. Most of my concerns
about the core stuff are adressed at this point (though I didn't look at
individual drivers). The fbcon resize stuff is still broken in subtle ways,
but that shouldn't prevent merging what we have now.
Ben.
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
prev parent reply other threads:[~2004-01-14 5:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 1:33 [PATCH] kyrofb support Paul Mundt
2004-01-14 1:49 ` Andrew Morton
2004-01-15 0:31 ` James Simmons
2004-01-14 2:09 ` Andrew Morton
2004-01-14 2:28 ` Paul Mundt
2004-01-14 12:45 ` Geert Uytterhoeven
2004-01-15 0:34 ` James Simmons
2004-01-15 0:36 ` James Simmons
2004-01-14 4:58 ` 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=1074056156.765.23.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=jsimmons@infradead.org \
--cc=lethal@linux-sh.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).