From: Nils Faerber <nils.faerber@kernelconcepts.de>
To: linux-mtd@lists.infradead.org
Subject: JFFS2 support fro AT45* dataflash...
Date: Fri, 31 Aug 2007 10:19:32 +0200 [thread overview]
Message-ID: <46D7CF14.1010009@kernelconcepts.de> (raw)
Hi!
Just a quick question of verification ;)
We are planning a new hardware and have to choose our storage device.
Ideally we would like to use one of the AT45* serial data flashes
(currently in plan is AT45DB642D with uclinux 2.6.xx).
Looking through the kernel sources I found several "hints" that those
dataflashes should be supported by MTD and JFFS2.
Now I just read in tha datasheet that dataflashes require a sector
rewrite every 10,000 write cycles in any of the pages of a single sector.
This seems complex to me and I was not able to conclusively figure out
for sure if MTD/JFFS2 supports this. JFFS2 is critical for our application.
So if someone could just briefly acknowledge that this sector-rewrite is
also implemented I would be extremely happy (and continue to go for data
flashes ;)
Many thanks!
Cheers
nils faerber
--
kernel concepts GbR Tel: +49-271-771091-12
Sieghuetter Hauptweg 48 Fax: +49-271-771091-19
D-57072 Siegen Mob: +49-176-21024535
--
reply other threads:[~2007-08-31 8:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=46D7CF14.1010009@kernelconcepts.de \
--to=nils.faerber@kernelconcepts.de \
--cc=linux-mtd@lists.infradead.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.