public inbox for linuxppc-dev@ozlabs.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Sebastian Siewior <linuxppc-embedded@ml.breakpoint.cc>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: loading NOR flash from DT
Date: Thu, 18 Oct 2007 00:23:23 +0400	[thread overview]
Message-ID: <47166F3B.2080904@ru.mvista.com> (raw)
In-Reply-To: <20071017195542.GA5501@Chamillionaire.breakpoint.cc>

Sebastian Siewior wrote:

>>>I have here a MPC8544 DS board with NOR flash on it and Kumar's git
>>>tree. I'm trying to detect this flash with the physmap_of module. I
>>>added a nor_flash block (I used sequoia.dts as an example) into my
>>>device tree on the same level as soc8544 or memory (or between them).
>>>After modprobing physmap_of nothing happend. Then I tried to make a tree
>>>with plb -> opb -> ebc and finally nor_flash but still nothing changed.
>>>
>>>Is there a user space dependency or did I just edit my device tree the
>>>wrong way? Any hints are welcome :)
>>
>>Post your device tree please.  I don't recall MPC8544 even having PLB,
>>OPB, or EBC busses, so they likely aren't getting probed.

[...]
> 	flash@fc000000 {
> 			compatible = "amd,s29gl512n", "cfi-flash";
> 			reg = <fc000000 4000000>;
> 			bank-width = <2>;
> 			#address-cells = <1>;
> 			#size-cells = <1>;
> 			fs@0 {
> 					label = "fs";
> 					reg = <0 f80000>;
> 			};
> 			firmware@f80000 {
> 					label ="firmware";
> 					reg = <f80000 80000>;
> 					read-only;
> 			};

    This looks good, so the problem is it doesn't get registered by the 
platform code as I've said.

WBR, Sergei

  parent reply	other threads:[~2007-10-17 20:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-17 19:26 loading NOR flash from DT Sebastian Siewior
2007-10-17 19:47 ` Josh Boyer
2007-10-17 19:55   ` Sebastian Siewior
2007-10-17 20:17     ` Scott Wood
2007-10-17 20:23     ` Sergei Shtylyov [this message]
2007-10-17 19:54 ` Sergei Shtylyov
2007-10-18  7:57   ` Sebastian Siewior

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=47166F3B.2080904@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=linuxppc-embedded@ml.breakpoint.cc \
    --cc=linuxppc-embedded@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