From: akuster <akuster@dslextreme.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Ralph Blach <rcblach@us.ibm.com>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Changes to "The plan"
Date: Tue, 30 Jul 2002 21:00:07 -0700 [thread overview]
Message-ID: <3D4760C7.7070001@dslextreme.com> (raw)
In-Reply-To: 20020731013958.GI27711@zax
David Gibson wrote:
> On Tue, Jul 30, 2002 at 08:02:42AM -0400, Ralph Blach wrote:
>
>>Armin
>>
>>It has always been my contention the the 4xx should be organized in the
>>following structure
>>Core
>>Chip
>>board
>>
>>This would tree would then reflect the reallity of chip design methodology.
>>the 405 now has many variants
>>so it would be
>>405 Core
>> Chip
>> 405CR
>> 405GP
>> Board
>> Walnut
>> .
>> .
>> .
>> NPE405L
>> .
>> .
>> .
>>
>
> It's not clear to me what you're proposing. Are you talking about the
> layout of the Config.in options, the layout of the .c files in various
> directories or the call structure of the platform initialization code?
>
>
Well, the lastest 2.5 model working after having some local discusions is:
board files are in /platforms/4xx such as walnut.*, ebony.*
implimentation files are in /kernel/4xx such as ibm405gp.*, ibm44gp.*,
ppc4xx_* & ppc405_*, I guess head should go there too.
the core files like ibm4xx, ibm405.h & ibm440.h are in include/asm-ppc
as well as ibm_ocp.h
Things like ocp.c and ocp_proc will most likely end up in drivers/ocp
since ocp can support more than just ppc.
comments
armin
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-07-31 4:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 12:02 Changes to "The plan" Ralph Blach
2002-07-30 16:48 ` Dan Malek
2002-07-31 1:31 ` Paul Mackerras
[not found] ` <OFA1123D85.667B22FB-ON85256C06.004182DD@raleigh.ibm.com>
2002-07-31 1:39 ` David Gibson
2002-07-31 4:00 ` akuster [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-30 6:12 akuster
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=3D4760C7.7070001@dslextreme.com \
--to=akuster@dslextreme.com \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=rcblach@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.