From: "Richard Rauch" <rrauch@itrgmbh.de>
To: <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] General NAND Flash support?
Date: Mon, 15 Dec 2014 14:52:00 -0000 [thread overview]
Message-ID: <006e01d01876$c053a860$40faf920$@itrgmbh.de> (raw)
Hello,
I am not sure about NAND flash support of eCos Open Source Repository.
I found a few hints in the source code for NAND flash (mainly in jffs2
implementation), but nothing in general!
So I am not sure, if eCos is fully supporting NAND flashes?
Is there an open source driver for NAND flashes available, which implements
all aspects for NAND support (bad block management, wear levelling,...),
which is usable from higher level drivers (fs fat/jffs2) ?
Thanks
Richard
Richard Rauch
www.itrgmbh.com
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2014-12-15 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 14:52 Richard Rauch [this message]
2014-12-15 18:38 ` Frank Pagliughi
2014-12-15 22:19 ` Daniel Morris
2014-12-16 14:53 ` AW: " Richard Rauch
2014-12-16 20:11 ` Ross Younger
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='006e01d01876$c053a860$40faf920$@itrgmbh.de' \
--to=rrauch@itrgmbh.de \
--cc=ecos-discuss@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).