From: Markus Schaber <schabi@logix-tt.com>
To: eCos general discussion list <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] JFFS2, NAND and the flash_v2 branch
Date: Fri, 04 Apr 2008 15:49:00 -0000 [thread overview]
Message-ID: <20080404174612.5744b46a@kingfisher.sec.intern.logix-tt.com> (raw)
Hi,
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:
- struct nand_oobinfo is referenced in jffs2_fs_sb.h, but not defined
anywhere.
- os-ecos.h contains "#error no nand yet" when CONFIG_JFFS2_FS_NAND is
set.
Am I missing something?
Thanks,
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS
Fight against software patents in Europe! www.ffii.org
www.nosoftwarepatents.org
--
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:[~2008-04-04 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 15:49 Markus Schaber [this message]
2008-04-04 15:56 ` Chris Zimman
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=20080404174612.5744b46a@kingfisher.sec.intern.logix-tt.com \
--to=schabi@logix-tt.com \
--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).