From: Grant Likely <grant.likely@secretlab.ca>
To: Michael Bergandi <mbergandi@gmail.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
Dushara Jayasinghe <DusharaJ@optiscan.com>
Subject: Re: soc vs localbus for flash in device tree
Date: Mon, 23 Feb 2009 19:12:26 -0700 [thread overview]
Message-ID: <fa686aa40902231812v7544b728te019e70d16c521e1@mail.gmail.com> (raw)
In-Reply-To: <1c641bc80902231611j57d53abcx56b32439f26cdf8@mail.gmail.com>
On Mon, Feb 23, 2009 at 5:11 PM, Michael Bergandi <mbergandi@gmail.com> wrote:
>>
>> I'm working on the kernel version Linux-2.6.29-rc5 with U-Boot
>> 1.2.0-g88e21e7b-dirty.
>
> I recommend you use a more current version of U-Boot. That one is quite old.
>
>> Does the flash node HAVE to be within a localbus node or can it reside
>> within the soc node? I've been basing my work on mpc834x_mds.dts
>> And hence haven't defined a localbus node.
>
> I think it can be in either, but the most common place I've seen is in the
> soc node.
If flash hangs off the local bus, then it belongs in the local bus
node. It doesn't make any sense to put it in the SoC node because the
SoC node describes the internal memory mapped devices. The local bus
node should have a ranges property that describes the translation
between physical address and individual chip selects.
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
prev parent reply other threads:[~2009-02-24 2:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 23:31 soc vs localbus for flash in device tree Dushara Jayasinghe
2009-02-24 0:06 ` Ira Snyder
2009-02-24 3:47 ` Dushara Jayasinghe
2009-02-24 0:11 ` Michael Bergandi
2009-02-24 2:12 ` Grant Likely [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=fa686aa40902231812v7544b728te019e70d16c521e1@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=DusharaJ@optiscan.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mbergandi@gmail.com \
/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).