All of lore.kernel.org
 help / color / mirror / Atom feed
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 11:30:59 +0200	[thread overview]
Message-ID: <4316CA53.7070201@gmail.com> (raw)
In-Reply-To: <0ILR00B812WSF3@mmp1.samsung.com>

Hi Kyungmin,

please let me bother you with another question.
It's about scanning for bad blocks during reading/writing flash (/* TODO 
handling oob */...)
What's the possibility of having a bad block at r/w? OneNAND spec isn't 
very extensive regarding handling bad blocks beside the initial scan. 
Which things must/should be done by the flash driver, which ones by the 
file system in this case?
I would be very grateful if you could give me a brief outline, I'm 
afraid BBM is a bit "too new" for us because we are used to operate on 
plain NOR... :-)

Thanks,
Bernhard


PS: Kyungmin, sorry for double mail

  parent reply	other threads:[~2005-09-01  9:31 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 [this message]
2005-09-01 10:03           ` Kyungmin Park
2005-09-01 10:09             ` Bernhard Priewasser
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=4316CA53.7070201@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.