From: David Woodhouse <dwmw2@infradead.org>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] [MTD] [CHIPS] stm_flash: new ST PSD4256G compatible flash chip driver
Date: Sat, 19 Sep 2009 14:01:46 -0700 [thread overview]
Message-ID: <1253394106.6317.38.camel@macbook.infradead.org> (raw)
In-Reply-To: <8bd0f97a0909191328j6be58c20o9bf4a4c3aadb1634@mail.gmail.com>
On Sat, 2009-09-19 at 16:28 -0400, Mike Frysinger wrote:
>
> > Can't you do the same?
>
> afaik, it isnt JEDEC compliant either. you can find the data sheet
> here:
> http://www.st.com/stonline/products/literature/ds/8116/psd4256g6v.htm
>
> so if i created a probe function that created a fake cfi table and
> then called cfi_cmdset_0002(), you think the read/write/erase
> functions would work ?
At first glance, it looks like that would work, yes. It basically seems
to be the same command set, at its core.
> i dont see any mapping drivers that do this
> kind of thing. where can i find an example ?
The examples are cfi_probe.c and jedec_probe.c. We have no example of
setting it up _directly_ from a map driver, but that doesn't mean it
can't be done.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
next prev parent reply other threads:[~2009-09-19 21:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-13 10:59 [PATCH] [MTD] [CHIPS] stm_flash: new ST PSD4256G compatible flash chip driver Mike Frysinger
2009-09-19 20:08 ` David Woodhouse
2009-09-19 20:28 ` Mike Frysinger
2009-09-19 21:01 ` David Woodhouse [this message]
2009-09-22 23:05 ` Mike Frysinger
2009-09-22 23:20 ` David Woodhouse
2009-09-22 23:30 ` Mike Frysinger
2009-09-22 23:39 ` David Woodhouse
2009-09-23 4:49 ` [PATCH] mtd: jedec_probe: add PSD4256G6V id Mike Frysinger
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=1253394106.6317.38.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=vapier.adi@gmail.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