public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Pantelis Antoniou <panto@intracom.gr>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [RFC] NAND Flash
Date: Tue, 27 Apr 2004 10:08:20 +0300	[thread overview]
Message-ID: <408E06E4.2090308@intracom.gr> (raw)

Hello there.

As you remember earlier I have sent a small patch for the NAND
portion of u-boot.

This forced me to really take a hard look at the code and really
evaluate it.

The big problem with the code as it is its its tendancy not to
account properly for errors which are not only probable but
certain during the life of the device.

For example the current code cannot boot reliably from NAND
and the read and write routines are also unreliable.

It's basic assumption made that you can read/write from the NAND
at any position is false. This is impossible because of
the bad blocks that may force you to skip a bad sector.

I'm currently in the process of rewritting to actually make it
work reliably.

I can keep backwards compatibility with the old code but
you can only use it at your own risk.

I'm asking for any people currently working with NAND to comment
on the following points:

1. Do you read and write the NAND at arbitrary offsets?
   That means not in page boundaries.

2. Do you use the NAND boot command? It can be replaced by a copy and
   bootm sequence.

3. Do you use it as a raw device without employing ECC? Do you
   understand the implications?

4. What kind of filesystem do you use? JFFS2 & YAFS have different OOB
   placement of ECC and status bits?

5. What kind of bad block management options would you like? I'm thinking
   of implementing a bad block detection mechanism which would erase and
   test the whole chip for any bad blocks.
   Another command could also utilise ECC to detect borderline working
   pages and relocate them to avoid a permanent failure.

Awaiting your input...

Regards

Pantelis

             reply	other threads:[~2004-04-27  7:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-27  7:08 Pantelis Antoniou [this message]
2004-06-06 21:55 ` [U-Boot-Users] [RFC] NAND Flash Wolfgang Denk
2004-06-07  5:54   ` Pantelis Antoniou
  -- strict thread matches above, loose matches on Subject: below --
2004-04-27  7:42 Peter Billek
2004-04-27  7:45 ` Pantelis Antoniou
2004-04-27 11:46 VanBaren, Gerald
2004-04-27 12:39 Woodruff, Richard
2004-04-27 12:42 ` Pantelis Antoniou
2004-04-27 14:13   ` Wolfgang Denk
2004-04-27 12:46 Woodruff, Richard
2004-04-27 12:44 ` Pantelis Antoniou
2004-04-27 13:52 Dave Ellis

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=408E06E4.2090308@intracom.gr \
    --to=panto@intracom.gr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox