From: David Gibson <david@gibson.dropbear.id.au>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-embedded@lists.linuxppc.org,
Paul Mackerras <paulus@samba.org>,
Dan Malek <dan@embeddededge.com>
Subject: Re: Organisation of 4xx initialization code
Date: Sat, 17 Nov 2001 11:40:52 +1100 [thread overview]
Message-ID: <20011117114052.F12763@zax> (raw)
In-Reply-To: <20011116075917.A5410@cpe-24-221-152-185.az.sprintbbd.net>
On Fri, Nov 16, 2001 at 07:59:17AM -0700, Tom Rini wrote:
>
> On Fri, Nov 16, 2001 at 04:46:26PM +1100, David Gibson wrote:
>
> > At the moment the initialization for each of the 4xx boards goes
> > through the platform_init() in arch/ppc/kernel/ppc4xx_setup.c, which
> > in turns calls a board_init() function for the specific board.
> >
> > It seems to me that it would make more sense to put platform_init() in
> > the board specific files, and these functions could then call back,
> > where appropriate, to generic 4xx setup functions. This would mean:
>
> But 95% of the current 4xx platform_init is generic. With the exception
> of the redwood kbd init stuff, which right now we could probably move
> into the redwood board_init (providing redwood_irkb_init sets things to
> NULL which the previous bits set).
And the common stuff can still be shared - it's just that the board
code, which clearly knows more about the configuration than the 4xx
generic stuff, chooses what order to do things in.
> > - We should be able to remove some inconvenient header
> > dependencies - at present lots of things are recompiled when board
> > local defines are changed because walnut.h/ep405.h/etc are included
> > indirectly in serial.h and some other unexpected places.
>
> Keep in mind <asm/ibm4xx.h> has the same exact thing. As does
> <asm/mpc8xx.h>. There's lots of wierd header dependancies, and it's not
> fixable in 2.4 anyhow. kbuild-2.5 doesn't have this issue, and this
> isn't even much of a problem anyhow.
Um, no, this has nothing to do with the build system. Board specific
header files, which contain largely information which is irrelevant to
everything except the board and 4xx setup code is being indirectly
included in parts of the generic kernel. That creates a dependency
regardless of the build system.
--
David Gibson | For every complex problem there is a
david@gibson.dropbear.id.au | solution which is simple, neat and
| wrong. -- H.L. Mencken
http://www.ozlabs.org/people/dgibson
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-17 0:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-16 5:46 Organisation of 4xx initialization code David Gibson
2001-11-16 11:57 ` Matt Porter
2001-11-16 15:51 ` Tom Rini
2001-11-16 16:42 ` Matt Porter
2001-11-16 17:13 ` Tom Rini
2001-11-16 23:24 ` Dan Malek
2001-11-17 0:43 ` David Gibson
2001-11-17 1:01 ` Dan Malek
2001-11-17 2:18 ` Tom Rini
2001-11-17 11:16 ` Paul Mackerras
2001-11-17 12:43 ` Ralph Blach
2001-11-17 14:46 ` Mark Pilon
2001-11-17 0:50 ` David Gibson
2001-11-17 2:16 ` Tom Rini
2001-11-17 0:35 ` David Gibson
2001-11-17 2:18 ` Tom Rini
2001-11-16 16:07 ` Mark Pilon
2001-11-16 17:29 ` Tom Rini
2001-11-16 14:59 ` Tom Rini
2001-11-17 0:40 ` David Gibson [this message]
2001-11-17 2:15 ` Tom Rini
2001-11-16 16:46 ` Dan Malek
2001-11-17 0:47 ` David Gibson
2001-11-17 1:11 ` Dan Malek
2001-11-16 17:15 ` Armin Kuster
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=20011117114052.F12763@zax \
--to=david@gibson.dropbear.id.au \
--cc=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=paulus@samba.org \
--cc=trini@kernel.crashing.org \
/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).