All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Becky Bruce <becky.bruce@freescale.com>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH] [POWERPC] Fix interrupt routing and setup of ULI M1575 on FSL boards
Date: Tue, 11 Sep 2007 14:36:07 -0500	[thread overview]
Message-ID: <20070911193607.GA13105@lixom.net> (raw)
In-Reply-To: <24F46474-1425-4C8B-A400-4D18D28932F2@freescale.com>

On Tue, Sep 11, 2007 at 01:43:59PM -0500, Becky Bruce wrote:

> >> Maybe it would make more sense for you guys to slice the platforms
> >> differently, and have a common platform for the eval boards you have
> >> with ULi on them instead of grouping it by core used by the processor
> >> on the board.
> >>
> >> (In other words, move 86xx over under 85xx, since there wouldn't be
> >> much
> >> left over anyway).
> >
> > Moving 86xx (classic 74xx core) under 85xx (book e500 core) makes
> > even less sense to me.
> 
> Yeah, that makes *no* sense to me either.  It's an unfortunate  
> artifact of the naming of boards to include the core name.  While the  
> devices and boards may be similar, once you have bookE vs non-bookE  
> cores, they become quite different.

It doesn't make sense if you move 86xx under 85xx right now, no.

What I meant (but didn't write) was more along the lines of forking off
a new platform (I don't know if you have a common code name for the SoC
side, but fsl-whatever) that contains the SoC and board support for the
parts and boards that share much (looks like the latest gen 85xx and
8641 would be candidates).

Looks like the CPM2-based stuff could be candidates for something similar
as well, but there's less activity there so there's less reason to rework
those, I suppose.

Of course, down the road I'm sure there'll be a part that contains 75%
of the current SoC, plus something new. And the next gen after that only
contains the 25% non-shared plus 75% brand new stuff and it all falls
apart. Not knowing your roadmap I have a hard time judging if that's
likely though. :-)


-Olof

  parent reply	other threads:[~2007-09-11 19:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-17  5:03 [PATCH] [POWERPC] Fix interrupt routing and setup of ULI M1575 on FSL boards Kumar Gala
2007-08-17  8:07 ` Paul Mackerras
2007-08-17 12:50   ` Kumar Gala
2007-08-17 23:53     ` Paul Mackerras
2007-08-18  5:30       ` Kumar Gala
2007-09-11 17:20 ` Olof Johansson
2007-09-11 18:00   ` Kumar Gala
2007-09-11 18:22     ` Olof Johansson
2007-09-11 18:33       ` Kumar Gala
2007-09-11 18:43         ` Becky Bruce
2007-09-11 19:08           ` Kumar Gala
2007-09-11 19:22             ` Becky Bruce
2007-09-11 19:38               ` Josh Boyer
2007-09-11 19:45               ` Olof Johansson
2007-09-11 19:47               ` Kumar Gala
2007-09-11 19:36           ` Olof Johansson [this message]
2007-09-12  6:33 ` [PATCH] [POWERPC] Fix interrupt routing and setup of ULI M1575 onFSL boards Swarthout Edward L-SWARTHOU

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=20070911193607.GA13105@lixom.net \
    --to=olof@lixom.net \
    --cc=becky.bruce@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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 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.