From: Vahid Fereydunkolahi <fereydunk@yahoo.com>
To: linux-mtd@lists.infradead.org
Subject: two questions about jffs2
Date: Tue, 3 May 2005 17:15:38 -0700 (PDT) [thread overview]
Message-ID: <20050504001538.77696.qmail@web51001.mail.yahoo.com> (raw)
Hi,
How does jffs2 handle the bad blocks on the NAND
flash? ( I noticed that at initialization jffs2 scans
the devivce and creates a bad block list, but it never
uses the bad block list. It seems that if the block is
bad it is not put into the block list).
Does current jffs2 and mtd support the NAND devices
with Page size more than 528 bytes?
Regards,
--vahid
__________________________________
Do you Yahoo!?
Make Yahoo! your home page
http://www.yahoo.com/r/hs
next reply other threads:[~2005-05-04 0:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-04 0:15 Vahid Fereydunkolahi [this message]
2005-05-04 8:39 ` two questions about jffs2 Artem B. Bityuckiy
-- strict thread matches above, loose matches on Subject: below --
2005-05-04 17:32 Vahid Fereydunkolahi
2005-05-04 19:07 Michael
2005-05-04 20:18 Vahid Fereydunkolahi
2005-05-04 20:43 ` Josh Boyer
2005-05-11 21:51 ` Thomas Gleixner
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=20050504001538.77696.qmail@web51001.mail.yahoo.com \
--to=fereydunk@yahoo.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox