From: Stefan Roese <sr@denx.de>
To: linuxppc-dev@ozlabs.org
Cc: Olof Johansson <olof@lixom.net>
Subject: Re: [PATCH 2/3] [POWERPC] Add AMCC Kilauea eval board support to platforms/40x
Date: Tue, 9 Oct 2007 13:34:16 +0200 [thread overview]
Message-ID: <200710091334.16682.sr@denx.de> (raw)
In-Reply-To: <20071008193404.GA10348@lixom.net>
Hi Olof,
On Monday 08 October 2007, Olof Johansson wrote:
> > +config KILAUEA
> > + bool "Kilauea"
> > + depends on 40x
> > + default y
> > + select 405EX
> > + help
> > + This option enables support for the AMCC PPC405EX evaluation board.
> > +
> > #config REDWOOD_5
> > # bool "Redwood-5"
> > # depends on 40x
> > @@ -89,14 +97,17 @@ config 403GCX
> > #depends on OAK
> > select IBM405_ERR51
> >
> > +config 405EP
> > + bool
> > +
> > +config 405EX
> > + bool
> > +
>
> Do you really need config options for 405EP/EX? I don't seem them used
> anywhere else in the code (and it's also contradictory to the whole new
> multiplatform way of looking at stuff :).
>
> I know the 405/440 is still somewhat #ifdef:ed on the cpu here and there,
> but since this doesn't add any such code I don't see a need for the config
> options?
Yes, I'm still used to needing these defines from arch/ppc (for example for
the 4xx EMAC driver). But its possible, that we really don't need it at all
in arch/powerpc with all the device tree information. Not sure though.
Josh, what do you think? Should I remove the 405EX define completely?
Best regards,
Stefan
next prev parent reply other threads:[~2007-10-09 11:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 9:08 [PATCH 2/3] [POWERPC] Add AMCC Kilauea eval board support to platforms/40x Stefan Roese
2007-10-08 11:48 ` Stephen Rothwell
2007-10-08 12:03 ` Stefan Roese
2007-10-08 19:34 ` Olof Johansson
2007-10-09 11:34 ` Stefan Roese [this message]
2007-10-10 19:44 ` Josh Boyer
2007-10-11 6:06 ` Stefan Roese
2007-10-10 20:23 ` Josh Boyer
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=200710091334.16682.sr@denx.de \
--to=sr@denx.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.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).