From: "Chris Zimman" <czimman@bloomberg.com>
To: "Markus Schaber" <schabi@logix-tt.com>,
"eCos general discussion list"
<ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] JFFS2, NAND and the flash_v2 branch
Date: Fri, 04 Apr 2008 15:56:00 -0000 [thread overview]
Message-ID: <F31C1582037F5041B0CD525FD870AE6A774285@ny2545.corp.bloomberg.com> (raw)
In-Reply-To: <20080404174612.5744b46a@kingfisher.sec.intern.logix-tt.com>
> In my recent research, I now came to the conclusion that NAND support
> for JFFS2 is not finished in the flash_v2 branch. Two examples:
Last time I checked, and this may not currently be correct, JFFS2 in anon CVS
doesn't work, and it wasn't finished. A finished and working JFFS2 is part
of eCosPro.
--Chris
--
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 prev parent reply other threads:[~2008-04-04 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 15:49 Markus Schaber
2008-04-04 15:56 ` Chris Zimman [this message]
2008-04-04 16:51 ` Jonathan Larmour
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=F31C1582037F5041B0CD525FD870AE6A774285@ny2545.corp.bloomberg.com \
--to=czimman@bloomberg.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=schabi@logix-tt.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 read-only IMAP folder(s) and NNTP newsgroup(s).