linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Vitaly Wool <vwool@ru.mvista.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] adding ROM chips to device tree
Date: Thu, 02 Nov 2006 23:23:24 +0300	[thread overview]
Message-ID: <1162499004.2592.2.camel@barja> (raw)
In-Reply-To: <454A4266.8040505@ru.mvista.com>


>     Also remember that we're not describing "physmap" compatible devices only.

No we are. This description fits nothing else but memory-mapped flashes.

Vitaly

  reply	other threads:[~2006-11-02 20:23 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
2006-11-02 13:45   ` Vitaly Wool
2006-11-02 19:09   ` Sergei Shtylyov
2006-11-02 20:23     ` Vitaly Wool [this message]
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=1162499004.2592.2.camel@barja \
    --to=vwool@ru.mvista.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=sshtylyov@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).