From: Dan Malek <dan@embeddededge.com>
To: Ralph Blach <rcblach@us.ibm.com>
Cc: akuster@dslextreme.com, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Changes to "The plan"
Date: Tue, 30 Jul 2002 12:48:47 -0400 [thread overview]
Message-ID: <3D46C36F.9000302@embeddededge.com> (raw)
In-Reply-To: OFA1123D85.667B22FB-ON85256C06.004182DD@raleigh.ibm.com
Ralph Blach wrote:
> It has always been my contention the the 4xx should be organized in the
> following structure
I know, and like I have said in the past that doesn't fit into the rest
of the PowerPC strucuture very well. We have processor parts and we have
boards (or platforms), that we can mix and match in a variety of ways.
There are other board vendors that want the exact opposite, since they
have a single board that can have a variety of different processors.
We currently separate the processors from the boards, so either of the
views will work. The configuration scripts determine how we "view"
the underlying structure. Currently, you select a processor type, and
then we provide a board selection to go with that, which is exactly
what you are asking for.
> This would tree would then reflect the reallity of chip design methodology.
The reality of chip design is they are becoming more integrated, things that
used to be on a board are now on a chip. Logically no different to a
system configurator. Our current configuration method simply asks for a
board type to reduce the number of configuration questions to be answered.
We could just as easily have a configurator that asks lots of questions
about the peripherals that need to be supported, and the underlying
directory structure wouldn't have to change.
> the 405 now has many variants
Doesn't matter to us, we can deal with that today. There are lots
of variants of other PowerPC chips as well, and we found ways to
make them look _less_ different, requiring fewer configuration options
and a less complex directory structure. You may want to consider
doing the same. Please don't confuse the marketing enjoyment of
lots of variants with the software necessary to support them.
Thanks.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-07-30 16:48 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 [this message]
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
-- 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=3D46C36F.9000302@embeddededge.com \
--to=dan@embeddededge.com \
--cc=akuster@dslextreme.com \
--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 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).