From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Vitaly Wool <vwool@ru.mvista.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] adding ROM chips to device tree
Date: Thu, 02 Nov 2006 07:30:37 -0600 [thread overview]
Message-ID: <1162474237.11351.7.camel@zod.rchland.ibm.com> (raw)
In-Reply-To: <20061102145539.f0b8657f.vwool@ru.mvista.com>
On Thu, 2006-11-02 at 14:55 +0300, Vitaly Wool wrote:
> In fact, currently this description can handle only flash devices mapped into memory in a linear way.
> For NAND flashes we'll need a whole lot different description but let's solve problems as they arise
> since I'm not aware of any ppc board w/ NAND chip yet :)
Um... all of the 440EP and 440EPx boards have NAND. And those have
been around for a while...
> +
> + Required properties:
> +
> + - device_type : has to be "rom"
Why "rom" instead of "NOR"?
> + - compatible : Should be the name of the MTD driver. Currently, this is
> + most likely to be "physmap".
> + - reg : Offset and length of the register set for the device.
reg doesn't really describe a register set here. It's the overall
memory space for flash.
> +
> + Recommended properties :
> +
> + - bank-width : Width of the flash data bus in bytes. Must be specified
> + for the NOR flashes.
This is a required property, not a recommended one.
josh
next prev parent reply other threads:[~2006-11-02 13:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-02 11:55 [PATCH] adding ROM chips to device tree Vitaly Wool
2006-11-02 13:30 ` Josh Boyer [this message]
2006-11-02 13:45 ` Vitaly Wool
2006-11-02 19:09 ` Sergei Shtylyov
2006-11-02 20:23 ` Vitaly Wool
2006-11-07 18:29 ` Sergei Shtylyov
2006-11-02 15:31 ` Grant Likely
2006-11-02 15:53 ` Vitaly Wool
2006-11-02 19:01 ` Sergei Shtylyov
2006-11-02 20:30 ` Vitaly Wool
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=1162474237.11351.7.camel@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=vwool@ru.mvista.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).