linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: David Gibson <dwg@au1.ibm.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 0/3] Initial AMCC Bamboo support
Date: Mon, 14 May 2007 20:38:33 -0500	[thread overview]
Message-ID: <1179193113.3420.95.camel@zod.rchland.ibm.com> (raw)
In-Reply-To: <20070515012629.GC565@localhost.localdomain>

On Tue, 2007-05-15 at 11:26 +1000, David Gibson wrote:
> On Mon, May 14, 2007 at 09:56:48AM -0500, Josh Boyer wrote:
> > Hi All,
> > 
> > The following patches add the initial AMCC Bamboo eval board support.  
> > 
> > The support for peripheral devices at the moment is rather limited as
> > the board is quite complicated in it's muxing of I/O lines.  Until the
> > bootwrapper can figure out how to setup the EBC peripherals based on the
> > dip switch settings, the DTS will lack any EBC devices.
> 
> Ick.  Can you describe roughly the setup here?  It might be that the
> simplest approach is to include all options in the DTS, and delete
> ones that aren't selected from the bootwrapper.

There's 3 switches that directly control the EBC memory map, and a
handful of other pin strap registers add to that.  To further complicate
things, there are two passes of the Bamboo board and the settings mean
different things to the individual board revisions.

By comparison, there's about 350 lines of code in U-Boot to do the setup
of the EBC.  It's not horrible, but I'm not sure it wants to be
duplicated in the wrapper either.

> I have a patch which might help here, which fills in the ebc's
> 'ranges' property based on the contents of the EBC bridge registers.
> I'm using it as part of the code necessary to get the right address
> for the Ebony flash depending on DIP switch settings.

Ooh... that's actually what I was thinking of doing.  Though I was
planning on poking individual nodes' regs properties instead.

josh

  reply	other threads:[~2007-05-15  1:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-14 14:56 [PATCH 0/3] Initial AMCC Bamboo support Josh Boyer
2007-05-14 14:57 ` [PATCH 1/3] Bamboo DTS Josh Boyer
2007-05-14 15:21   ` Segher Boessenkool
2007-05-14 15:52     ` Segher Boessenkool
2007-05-14 18:44     ` Josh Boyer
2007-05-14 14:59 ` [PATCH 2/3] Bamboo platform support Josh Boyer
2007-05-15  0:58   ` Stephen Rothwell
2007-05-15  1:03     ` Josh Boyer
2007-05-15  2:03       ` Stephen Rothwell
2007-05-15  2:42         ` Josh Boyer
2007-05-14 14:59 ` [PATCH 3/3] Bamboo wrapper Josh Boyer
2007-05-15  1:28   ` David Gibson
2007-05-15  1:29     ` Josh Boyer
2007-05-15  1:26 ` [PATCH 0/3] Initial AMCC Bamboo support David Gibson
2007-05-15  1:38   ` Josh Boyer [this message]
2007-05-15  1:44     ` David Gibson
2007-05-15  7:33       ` Benjamin Herrenschmidt

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=1179193113.3420.95.camel@zod.rchland.ibm.com \
    --to=jwboyer@linux.vnet.ibm.com \
    --cc=dwg@au1.ibm.com \
    --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).