linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: David Gibson <dwg@au1.ibm.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 0/3] Initial AMCC Bamboo support
Date: Tue, 15 May 2007 17:33:07 +1000	[thread overview]
Message-ID: <1179214387.32247.168.camel@localhost.localdomain> (raw)
In-Reply-To: <20070515014431.GF565@localhost.localdomain>


> You may need to do both.  At least if you use the same format for the
> ebc binding as I have on Ebony: in the reg properties of the
> individual nodes I directly encode the ebc chip select value and
> offset within the peripheral bank.  The ebc node's 'ranges' gives the
> mappings into the OPB space.  So, in practice, the low 20 bits of
> address are determined by the individual peripheral's reg properties,
> and the upper 12 bits are determined by the ranges property at the EBC
> node.

In addition we might want a helper to fix the node unit address after
poking reg ...

Ben.

      reply	other threads:[~2007-05-15  7:33 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
2007-05-15  1:44     ` David Gibson
2007-05-15  7:33       ` Benjamin Herrenschmidt [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=1179214387.32247.168.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --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).