From: Kim Phillips <kim.phillips@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 4/7] Add MPC8360EMDS board support (try 2)
Date: Wed, 4 Oct 2006 16:16:07 -0500 [thread overview]
Message-ID: <20061004161607.6eeaa51f.kim.phillips@freescale.com> (raw)
In-Reply-To: <CEA95FBE-ED7E-4512-A6C5-6362DAE69744@kernel.crashing.org>
On Tue, 3 Oct 2006 23:27:42 -0500
Kumar Gala <galak@kernel.crashing.org> wrote:
>
> On Oct 3, 2006, at 11:17 PM, Kim Phillips wrote:
>
<snip>
> > arch/powerpc/platforms/83xx/mpc8360e_pb.c | 220 ++++++
> > arch/powerpc/platforms/83xx/mpc8360e_pb.h | 23 +
> > 3 files changed, 1261 insertions(+), 0 deletions(-)
>
> What's the point of the mpc8360e_pb.h if there's nothing in it?
>
well I thought I was being consistent with the other 83xx boards ;)
> Also, any reason the files are _pb and config is emds?
>
_pb == processor board, the core of the mds (modular development system). The pb can be operated independently of the rest of what comprises the mds.
I used mds nomenclature in 832x since the support includes parts of the mds that are separate from just the pb, e.g. the pci bits in the device tree.
but we need to be more consistent, I agree.
also, there is a wealth of duplicated platform code among each of the four 83xx platforms. Somethings wrong when one duplicates a file just to s/836/832/g. How about consolidating them all down to one mpc83xx_mach.c file that enables potential board quirks based on the dev tree root's model property? That will eliminate all the redundant code, and get rid of the file naming inconsistencies.
Kim
prev parent reply other threads:[~2006-10-04 21:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 4:17 [PATCH 4/7] Add MPC8360EMDS board support (try 2) Kim Phillips
2006-10-04 4:27 ` Kumar Gala
2006-10-04 21:16 ` Kim Phillips [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=20061004161607.6eeaa51f.kim.phillips@freescale.com \
--to=kim.phillips@freescale.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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).