From: Vitaly Wool <vwool@ru.mvista.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] adding ROM chips to device tree
Date: Thu, 02 Nov 2006 18:53:58 +0300 [thread overview]
Message-ID: <1162482838.2592.0.camel@barja> (raw)
In-Reply-To: <528646bc0611020731g26198316y5e162fff487e416b@mail.gmail.com>
> What about selecting driver; ie. CFI vs. non-CFI FLASH devices?
> (Although I'm not sure that it really matters).
It's all left for physmap to handle.
Vitaly
next prev parent reply other threads:[~2006-11-02 15:54 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
2006-11-07 18:29 ` Sergei Shtylyov
2006-11-02 15:31 ` Grant Likely
2006-11-02 15:53 ` Vitaly Wool [this message]
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=1162482838.2592.0.camel@barja \
--to=vwool@ru.mvista.com \
--cc=grant.likely@secretlab.ca \
--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;
as well as URLs for NNTP newsgroup(s).