From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <segher@kernel.crashing.org>
Received: from mail-in-06.arcor-online.net (mail-in-06.arcor-online.net
	[151.189.21.46])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client CN "mx.arcor.de",
	Issuer "Thawte Premium Server CA" (verified OK))
	by ozlabs.org (Postfix) with ESMTP id 3CD03DDFC7
	for <linuxppc-dev@ozlabs.org>; Fri,  4 May 2007 04:08:31 +1000 (EST)
In-Reply-To: <463A2192.6020308@ru.mvista.com>
References: <20070501051804.GB3881@localhost.localdomain>	<4639CBD8.6010205@ru.mvista.com>	<20070503123055.GE26659@localhost.localdomain>	<4639DDE1.40904@ru.mvista.com>	<71e4c68de5240a652b561d8cfa2e05f3@kernel.crashing.org>
	<463A1941.3090608@ru.mvista.com> <463A2192.6020308@ru.mvista.com>
Mime-Version: 1.0 (Apple Message framework v623)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <e21cca984c076474a6e89018a198d93a@kernel.crashing.org>
From: Segher Boessenkool <segher@kernel.crashing.org>
Subject: Re: powerpc_flash_init(), wtf!?
Date: Thu, 3 May 2007 20:07:27 +0200
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: linuxppc-dev@ozlabs.org, David Gibson <david@gibson.dropbear.id.au>
List-Id: Linux on PowerPC Developers Mail List <linuxppc-dev.ozlabs.org>
List-Unsubscribe: <https://ozlabs.org/mailman/listinfo/linuxppc-dev>,
	<mailto:linuxppc-dev-request@ozlabs.org?subject=unsubscribe>
List-Archive: <http://ozlabs.org/pipermail/linuxppc-dev>
List-Post: <mailto:linuxppc-dev@ozlabs.org>
List-Help: <mailto:linuxppc-dev-request@ozlabs.org?subject=help>
List-Subscribe: <https://ozlabs.org/mailman/listinfo/linuxppc-dev>,
	<mailto:linuxppc-dev-request@ozlabs.org?subject=subscribe>

>>     Yeah, you're right here, and I've probably misunderstood what 
>> "memory" node was. In fact, the flash in my system resides on the 
>> same local bus as RAM, so the proper place would be behind the "lbc" 
>> (or whatever -- it doesn't exist as yet) node on the "soc" bus.  Do 
>> you think I need to go and document it as well for such cause? :-]
>
>    No, that probably won't do. MPC85xx SoC bus has ranges = <e0000000 
> 00100000> and the NOR flash is mapped at 0xff000000, so it seems that 
> it can't be located under the "soc" bus (unless that latter has 
> "ranges" prop extended?).

If the RAM and/or ROM sit on the SoC bus, the "ranges"
property in the SoC node should be able to translate
their addresses, yes.  You could opt for having the
memory controller a separate device node, as a sibling
of the "soc" node, if that agrees better with your
SoC architecture.  "It all depends".


Segher