All of lore.kernel.org
 help / color / mirror / Atom feed
From: Woodruff, Richard <r-woodruff2@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] PATCH : Fixes and enhancements for NAND flash.
Date: Thu, 24 Jul 2003 18:57:51 -0500	[thread overview]
Message-ID: <FD2AC9A020DDD51194710008C7089B200BEE2218@dlee17.itg.ti.com> (raw)

Hello,

The following path fixes a few bugs in cmd_nand.c :
  - Fixed null dereference which could result in incorrect ECC values.
  - Added support for devices with no Ready/Busy signal connected.
  - Added OMAP1510 read/write protect handling.
  - Fixed nand.h's ECCPOS. A conflict existed with POS5 and badblock for
non-JFFS2.
  - Switched default ECC to be JFFS2.
  - Added spinning wheel.
--------------------
Prior to this only ECC for JFFS2 would have worked, and that only if you had
memory at zero which you didn't mind being corrupted. The other method would
result in a corrupted bad block byte in the oob data.

Regards,

Richard W.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: nand_fix.diff
Type: application/octet-stream
Size: 10814 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20030724/5d70094f/attachment.obj 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nand_fix.changelog
Type: application/octet-stream
Size: 396 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20030724/5d70094f/attachment-0001.obj 

             reply	other threads:[~2003-07-24 23:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-24 23:57 Woodruff, Richard [this message]
2003-07-26 21:35 ` [U-Boot-Users] PATCH : Fixes and enhancements for NAND flash Wolfgang Denk
2003-07-27 13:20 Woodruff, Richard
2003-07-27 13:38 ` Wolfgang Denk
2003-07-27 16:30 Woodruff, Richard
2003-07-27 17:37 ` Wolfgang Denk
2003-07-27 17:53   ` Robert Schwebel
2003-07-27 18:25     ` Wolfgang Denk

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=FD2AC9A020DDD51194710008C7089B200BEE2218@dlee17.itg.ti.com \
    --to=r-woodruff2@ti.com \
    --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.