All of lore.kernel.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: David Gibson <dwg@au1.ibm.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 2/3] Derive ebc ranges property from EBC registers
Date: Wed, 16 May 2007 15:28:16 +0200	[thread overview]
Message-ID: <1c27b74b07962c94458f6a6eb2677cf4@kernel.crashing.org> (raw)
In-Reply-To: <20070515230930.GB20290@localhost.localdomain>

>> 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.

Or a subset of it, anyway; both address domains have to
use the same representation in "reg" properties, and the
mapping has to be 1-1.

A missing "ranges" property means there is no direct
mapping, which is more correct in this case, and perfectly
valid.

> If we're
> using the chip-select/offset addressing form for the EBC peripherals,
> that's manifestly not the case.

This would be a nice use case for the

	ranges = ??;

syntax when/if that gets added to DTC and the kernel
and bootwrapper parsers for DTBs.


Segher

  parent reply	other threads:[~2007-05-16 13:28 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
2007-05-16 13:28       ` Segher Boessenkool [this message]
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
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

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=1c27b74b07962c94458f6a6eb2677cf4@kernel.crashing.org \
    --to=segher@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 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.