public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mxs_nand: Fix ECC strength for NAND flash with OOB size of 224
Date: Tue, 10 Sep 2013 19:02:30 +0200	[thread overview]
Message-ID: <522F50A6.20105@denx.de> (raw)
In-Reply-To: <1377355884-5920-1-git-send-email-eliedebrauwer@gmail.com>

On 24/08/2013 16:51, Elie De Brauwer wrote:
> On a board with an i.mx28 and a Micron MT29F4G08ABAEAH4, Linux says:
> 
> NAND device: Manufacturer ID: 0x2c, Chip ID: 0xdc (Micron MT29F4G08ABAEAH4),
> 512MiB, page size: 4096, OOB size: 224) the ECC strength is 16.
> 
> root@(none):/sys/devices/virtual/mtd/mtd0# for i in ecc_strength oobsize subpagesize; do echo $i = `cat $i`; done
> ecc_strength = 16
> oobsize = 224
> subpagesize = 4096
> 
> The ECC strength was not properly discovered by U-Boot causing the data
> written by Linux to return an -74 (EBADMSG) when read from U-Boot. This
> patch fixes mxs_nand_get_ecc_strength() to function in case of a NAND
> flash with page_data_size = 4096 and page_oob_size= 224.
> 
> Signed-off-by: Elie De Brauwer <eliedebrauwer@gmail.com>
> ---

Scott, I found this is assigned to me in patchwork. Is it ok if I apply it ?

Best regards,
Stefano

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

  reply	other threads:[~2013-09-10 17:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-24 14:51 [U-Boot] [PATCH] mxs_nand: Fix ECC strength for NAND flash with OOB size of 224 Elie De Brauwer
2013-09-10 17:02 ` Stefano Babic [this message]
2013-09-10 20:11   ` Scott Wood
2013-09-11  7:24     ` Stefano Babic
2013-09-11 16:53       ` Scott Wood

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=522F50A6.20105@denx.de \
    --to=sbabic@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox