From: Olof Johansson <olof@lixom.net>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] [POWERPC] 85xx: Add basic Uniprocessor MPC8572 DS port
Date: Tue, 11 Sep 2007 12:15:21 -0500 [thread overview]
Message-ID: <20070911171521.GB10743@lixom.net> (raw)
In-Reply-To: <11B85E70-D643-4013-A9B3-59CD76F9D7AB@kernel.crashing.org>
On Tue, Sep 11, 2007 at 11:00:28AM -0500, Kumar Gala wrote:
>
> On Sep 11, 2007, at 10:55 AM, Olof Johansson wrote:
>
> > On Tue, Sep 11, 2007 at 10:50:18AM -0500, Kumar Gala wrote:
> >>> How different are these boards really? Could you just detect
> >>> MPC85xxDS
> >>> and have a generic platform for them, or are they different
> >>> enough that
> >>> you need individual ones for it?
> >>
> >> I wanted a different probe. I figured having a different struct
> >> was a
> >> simple solution.
> >
> > Seems like the only reason to need that is the setting of
> > primary_phb_addr. Can't that information be derived out of the device
> > tree instead? That'd avoid alot of code duplication (code that
> > includes
> > ifdefs, FWIW :-)
>
> well the ifdefs are orthogonal. We don't have a way of knowing
> primary from the device tree today.
How about something like "fsl,primary-phb" in the bus device node? I don't
know, maybe it's already been discussed and turned down for some reason.
Or would it be sufficient to check children of that device node to see
if the ULi is on that bus?
> > It just seems like a slippery slope. I'm not objecting directly to
> > this
> > patch, but I think it should be fixed for the longer term.
>
> Once we have a clean way of knowing primary PHB than I'm happy to fixup.
-Olof
next prev parent reply other threads:[~2007-09-11 17:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-11 6:29 [PATCH] [POWERPC] 85xx: Add basic Uniprocessor MPC8572 DS port Kumar Gala
2007-09-11 14:17 ` Scott Wood
2007-09-11 15:58 ` Kumar Gala
2007-09-12 13:20 ` Segher Boessenkool
2007-09-13 3:27 ` Kumar Gala
2007-09-13 16:53 ` Segher Boessenkool
2007-09-13 21:23 ` Kumar Gala
2007-09-11 14:18 ` Olof Johansson
2007-09-11 15:50 ` Kumar Gala
2007-09-11 15:55 ` Olof Johansson
2007-09-11 16:00 ` Kumar Gala
2007-09-11 17:15 ` Olof Johansson [this message]
2007-09-11 17:21 ` Scott Wood
2007-09-11 17:33 ` Olof Johansson
2007-09-11 17:48 ` Scott Wood
2007-09-11 17:59 ` Kumar Gala
2007-09-12 3:00 ` David Gibson
2007-09-12 3:35 ` Kumar Gala
2007-09-12 3:37 ` David Gibson
2007-09-12 3:37 ` Olof Johansson
2007-09-12 13:20 ` Segher Boessenkool
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=20070911171521.GB10743@lixom.net \
--to=olof@lixom.net \
--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