From: Thomas Gleixner <tglx@linutronix.de>
To: Olivier ERIBON <olivier.eribon@free.fr>, linux-mtd@lists.infradead.org
Subject: Re: Pb : JFFS2 & NAND with bad blocks
Date: Fri, 24 Jan 2003 08:04:45 +0100 [thread overview]
Message-ID: <200301240804.45513.tglx@linutronix.de> (raw)
In-Reply-To: <002e01c2c323$b3c99740$0200a8c0@windows>
On Thursday 23 January 2003 22:09, Olivier ERIBON wrote:
> Hi!
>
> I use the latest CVS MTD together with a 64MB NAND Flash and
> JFFS2 (from 2.4.18 Montavista kernel).
>
> I patch mtd only (without -j option in order to patch jffs2 because I have
> a problem with ZLIB)
That's the reason for your problem.
> [oeribon@serdnt25 linux-2.4.18_mvl30]$ grep JFFS2 .config
> CONFIG_JFFS2_FS=y
> CONFIG_JFFS2_FS_DEBUG=0
CONFIG_JFFS2_NAND=y is missing.
--
Thomas
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de
prev parent reply other threads:[~2003-01-24 6:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 21:09 Pb : JFFS2 & NAND with bad blocks Olivier ERIBON
2003-01-24 7:04 ` Thomas Gleixner [this message]
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=200301240804.45513.tglx@linutronix.de \
--to=tglx@linutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=olivier.eribon@free.fr \
/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