All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] [OneNAND] bad block aware read/write support
Date: Thu, 6 Nov 2008 10:33:58 +0100	[thread overview]
Message-ID: <200811061033.58383.sr@denx.de> (raw)
In-Reply-To: <9c9fda240811051513p5320a621u858f0208393cf9e3@mail.gmail.com>

On Thursday 06 November 2008, Kyungmin Park wrote:
> >> > +           ret = mtd->read_oob(mtd, ofs, &ops);
> >> > +           if (ret) {
> >> > +                   printk("Read failed 0x%x, %d", (unsigned int) ofs,
> >> > ret); +                   mtd->block_markbad(mtd, ofs);
> >
> > You are marking all blocks as bad whenever a failure occurs. I'm not sure
> > if we really should do it this way. Failures could have other reasons as
> > well. I'm inclined to remove this marking in my patch version.
> >
> > Any comments?
>
> Right, current implementation make a bad on all errors, but actually
> it need to try again in case read/write error. It will patch it later.

OK, I'll remove this bad block marking for now.

> > <snip>
> >
> >> I'm currently working on a version of this "bad block aware" OneNAND
> >> command support which resembles the NAND command style even more. I hope
> >> to have something ready till tomorrow that I can send to the list for
> >> review. I would really like to see some comments from you on this since
> >> you are much more experienced with the OneNAND stuff.
> >
> > Do you already have some comments to the patch version I posted
> > yesterday?
>
> Looks good to me. No problem to commit your version.
>
> Acked-by: Kyungmin Park <kyungmin.park@samsung.com>

Thanks. I'll send an updated version today or tomorrow.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

      reply	other threads:[~2008-11-06  9:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-04  0:04 [U-Boot] [PATCH] [OneNAND] bad block aware read/write support Kyungmin Park
2008-11-04  9:48 ` Stefan Roese
2008-11-05  8:40   ` Stefan Roese
2008-11-05 23:13     ` Kyungmin Park
2008-11-06  9:33       ` Stefan Roese [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=200811061033.58383.sr@denx.de \
    --to=sr@denx.de \
    --cc=u-boot@lists.denx.de \
    /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.