All of lore.kernel.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, David Gibson <dwg@au1.ibm.com>
Subject: Re: [patch 3/6] Walnut DTS
Date: Wed, 5 Sep 2007 13:38:16 +0200	[thread overview]
Message-ID: <412bb2e63637100c8d47595a19f888ae@kernel.crashing.org> (raw)
In-Reply-To: <1188952766.3223.3.camel@localhost.localdomain>

>> Hrm.. I'm still slightly uneasy though.  In my Ebony device tree, the
>> POB's ranges exists to embed the 32-bit OPB space into the 64-bit PLB
>> space by tacking on a 0x1 in bits 32:35.  In your 405gp ranges, you're
>> describing just the address range used by OPB peripherals
>> (0xef600000-0xf0000000) as residing at address 0 in OPB-space.
>>
>> Since the ranges will still generate the right physical addresses, I
>> guess it doesn't matter.  But I'm not sure it meets the principle of
>> least surprise - since I think the documentation generally talks as
>> though addresses on the 405 OPB bus are identical to addreses on the
>> PLB.
>
> I don't care either way.  If I remember correctly, this way of doing it
> came out of a discussion with Segher.

I don't think I ever said that this is a better way of doing things --
then again, I change my mind now and then.

Someone needs to write down a proposed device binding for these busses,
and then we can really discuss things ;-)


Segher

  reply	other threads:[~2007-09-05 11:39 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-31 20:04 [patch 0/6] Current 4xx patch queue Josh Boyer
2007-08-31 20:04 ` [patch 1/6] Fix bus probe on Bamboo board Josh Boyer
2007-09-03  0:58   ` David Gibson
2007-08-31 20:04 ` [patch 2/6] cuimage for " Josh Boyer
2007-09-03  1:01   ` David Gibson
2007-09-03 13:42     ` Josh Boyer
2007-09-05  1:10       ` David Gibson
2007-09-05  0:40         ` Josh Boyer
2007-09-05  5:46           ` David Gibson
2007-09-05  5:53             ` Josh Boyer
2007-09-05 16:42               ` Josh Boyer
2007-09-07  3:26                 ` David Gibson
2007-09-07  1:06               ` David Gibson
2007-08-31 20:04 ` [patch 3/6] Walnut DTS Josh Boyer
2007-09-03  1:08   ` David Gibson
2007-09-02 13:59     ` Josh Boyer
2007-09-04 12:42       ` Josh Boyer
2007-09-05  2:36         ` David Gibson
2007-09-05  0:39           ` Josh Boyer
2007-09-05 11:38             ` Segher Boessenkool [this message]
2007-09-05 16:33               ` Josh Boyer
2007-09-07  1:07                 ` David Gibson
2007-08-31 20:04 ` [patch 4/6] Walnut defconfig Josh Boyer
2007-08-31 20:04 ` [patch 5/6] Walnut board support Josh Boyer
2007-09-03  1:11   ` David Gibson
2007-09-02 13:59     ` Josh Boyer
2007-09-04 12:37       ` Josh Boyer
2007-09-05  1:09         ` David Gibson
2007-09-05  3:01   ` David Gibson
2007-08-31 20:04 ` [patch 6/6] Walnut zImage wrapper Josh Boyer
2007-09-03  1:13   ` David Gibson
2007-09-02 13:58     ` Josh Boyer
2007-09-05 16:36       ` Josh Boyer
2007-09-07  1:22         ` David Gibson
2007-09-24  7:49         ` Wolfgang Grandegger
2007-09-24 12:03           ` Josh Boyer
2007-09-24 12:20             ` Wolfgang Grandegger
2007-09-24 12:25               ` 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=412bb2e63637100c8d47595a19f888ae@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=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 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.