All of lore.kernel.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: Wed, 17 Oct 2007 23:54:08 +0400	[thread overview]
Message-ID: <47166860.6000705@ru.mvista.com> (raw)
In-Reply-To: <20071017192651.GA5192@Chamillionaire.breakpoint.cc>

Hello.

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

    I guess you were using quite recent kernel version where the file that 
published the node (arch/powerpc/sysdev/rom.c) had been already dremoved and 
and the platform code still didn't publish the on-board devices via 
of_platform_bus_probe().

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

    Add either of_platform_bus_probe() or platform_device_create() to 
arch/powerpc/platforms/85xx/85xx_ds.c.

> Is there a user space dependency or did I just edit my device tree the
> wrong way? Any hints are welcome :)

    You haven't cited your node, so no conclusion acn be made about it...

WBR, Sergei

  parent reply	other threads:[~2007-10-17 20:11 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
2007-10-17 19:54 ` Sergei Shtylyov [this message]
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=47166860.6000705@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 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.