mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Cristiano De Alti <cristiano_dealti@hotmail.com>
To: barebox@lists.infradead.org
Subject: i.MX21 ADS NAND flash bad blocks scan. Barebox vs Linux
Date: Thu, 13 Mar 2014 20:44:08 +0000 (UTC)	[thread overview]
Message-ID: <loom.20140313T212720-896@post.gmane.org> (raw)

Hi,
  I'm probably posting to the wrong list since this is Linux issue.
I'm still trying to revive this old board.

This board has a 64MBi Samsung NAND flash that is detected both by Barebox
(recent snapshot) and Linux 3.4.77.

The issue is that, while the bad blocks scan takes a negligible time on
Barebox, it takes 10 minutes to complete on Linux.
They both detect block 0 as a bad block. This is strange since it is
guaranteed to be good by the manufacturer but I've read the OOB data with
barebox and it's marked ad bad. I found this board in the lab and don't know
how it was used before.

Barebox code, nand_imx.c, and Linux code, mxc_nand.c, are similar but not
identical of course. I also think that Linux code was contributed by
Pengutronix so this is the reason I'm asking here.

I've enabled debug statements in Linux code and added my own statements.
As said, scan completes, everything looks OK but it is very slow.

Maybe someone has an idea.

Ciao




_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2014-03-13 20:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-13 20:44 Cristiano De Alti [this message]
2014-03-17  6:31 ` Sascha Hauer
2014-03-17 22:09   ` Cristiano De Alti
2014-03-17  6:43 ` Alexander Aring
2014-03-17 22:25   ` Cristiano De Alti
2014-03-18  6:22     ` Alexander Aring
2014-03-22 16:08 ` Cristiano De Alti

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=loom.20140313T212720-896@post.gmane.org \
    --to=cristiano_dealti@hotmail.com \
    --cc=barebox@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