From: Bernhard Priewasser <priewasser@gmail.com>
To: kyungmin.park@samsung.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] OneNAND: Simple Bad Block handling support
Date: Thu, 01 Sep 2005 12:09:37 +0200 [thread overview]
Message-ID: <4316D361.3030203@gmail.com> (raw)
In-Reply-To: <0IM4002SYUMFJ8@mmp2.samsung.com>
> I don't know the exactly but I heard that JFFS2 handles runtime
> badblock internally.
> So OneNAND MTD don't care badblock handling in read/write function.
> MTD only care the initial bad block at erase operation.
Isn't this rather important? :-) As I said, I'm rather new to the bad
block stuff, so I'm ashamed of don't knowing it at all. Can JFFS2
recognize a bad block without OneNAND driver explicitely reporting one??
I'm very interested in this thing; presumably it may be easy to find out
having a look on the list's NAND BBT threads...
> In our commercial software, we use another bad block handling, known
> as Bad Block Management (BBM) based on replace instead of skip as BBT
> So we don't care the intial bad and runtime bad.
> Now we are trying to implement our scheme and will be released at open
> source. But not yet available in this time.
You are speaking about RFS? I'm wondering for quite a time about the
technical and commercial parallels/differences of MTD/JFFS2 and RFS...
Do you have any (public) comment on the occurence of (runtime) bad
blocks? When, why, ...?
> If do you have any question. please let me know :)
Too many to write down, but I'll try ;-)
Regards,
Bernhard
next prev parent reply other threads:[~2005-09-01 10:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-18 8:16 [PATCH] OneNAND: Simple Bad Block handling support Kyungmin Park
2005-08-23 13:56 ` Bernhard Priewasser
2005-08-23 23:42 ` Kyungmin Park
2005-08-24 9:24 ` Bernhard Priewasser
2005-08-24 10:49 ` Bernhard Priewasser
2005-08-24 23:36 ` Kyungmin Park
2005-08-25 7:56 ` Bernhard Priewasser
2005-09-01 9:30 ` Bernhard Priewasser
2005-09-01 10:03 ` Kyungmin Park
2005-09-01 10:09 ` Bernhard Priewasser [this message]
2005-09-07 8:09 ` Bernhard Priewasser
2005-09-07 11:44 ` Kyungmin Park
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=4316D361.3030203@gmail.com \
--to=priewasser@gmail.com \
--cc=kyungmin.park@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.