From: David Gibson <dwg@au1.ibm.com>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 2/3] Derive ebc ranges property from EBC registers
Date: Wed, 16 May 2007 13:13:28 +1000 [thread overview]
Message-ID: <20070516031328.GA19127@localhost.localdomain> (raw)
In-Reply-To: <20070516022958.GB25075@crusty.rchland.ibm.com>
On Tue, May 15, 2007 at 09:29:59PM -0500, Josh Boyer wrote:
> On Wed, May 16, 2007 at 09:09:30AM +1000, David Gibson wrote:
> > > Do we want a "ranges;" here as a placeholder? I don't see where it's
> > > absolutely required, but it makes me feel better for some reason...
> >
> > Absolutely not. An empty ranges property indicates that the child bus
> > address space is the same as the parent bus address space. If we're
> > using the chip-select/offset addressing form for the EBC peripherals,
> > that's manifestly not the case.
>
> Ah ok. My lack of device tree experience showing through again.
>
> > > So this sets the ranges for the EBC bus, but not the "regs" properties
> > > of the child nodes. Without that, the child nodes will not be mapped to
> > > the correct addresses...
> >
> > Well, no, the child reg properties can't be deduced from the EBC
> > registers.
>
> Right, I didn't mean to imply the could be.
>
> > > Did you have a plan on how to fixup the child "regs" properties so that
> > > when the DIP switches are flipped around, the children show up
> > > correctly?
> >
> > Well, on Ebony (AFAICT), the only child reg property that might need
> > adjustment is the small flash. My MTD enabling patch includes some
> > code in the boot wrapper to toggle the appropriate bit in it's reg
> > property.
>
> Hm, ok. On Bamboo, it's more complicated. I'll have to think of something
> there I suppose.
Want to send me a board manual? I can see if any approach springs to
mind.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2007-05-16 3:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 4:52 [0/3] Ebony tweaks David Gibson
2007-05-15 4:54 ` [PATCH 2/3] Derive ebc ranges property from EBC registers David Gibson
2007-05-15 12:59 ` Josh Boyer
2007-05-15 23:09 ` David Gibson
2007-05-16 2:29 ` Josh Boyer
2007-05-16 3:13 ` David Gibson [this message]
2007-05-16 13:28 ` Segher Boessenkool
2007-05-15 4:54 ` [PATCH 1/3] Factor zImage's 44x reset code out of ebony.c David Gibson
2007-05-15 12:47 ` Josh Boyer
2007-05-15 4:54 ` [PATCH 3/3] Fixes to allow use of Ebony's flash chips through physmap_of David Gibson
2007-05-15 13:10 ` Josh Boyer
2007-05-15 23:10 ` David Gibson
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=20070516031328.GA19127@localhost.localdomain \
--to=dwg@au1.ibm.com \
--cc=jwboyer@linux.vnet.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).