All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] mtd:mxs:nand support oobsize bigger than 512
Date: Tue, 20 Jan 2015 12:03:49 +0100	[thread overview]
Message-ID: <201501201203.49418.marex@denx.de> (raw)
In-Reply-To: <1418963953-1623-2-git-send-email-Peng.Fan@freescale.com>

On Friday, December 19, 2014 at 05:39:13 AM, Peng Fan wrote:
> If ecc chunk data size is 512 and oobsize is bigger than 512, there is
> a chance that block_mark_bit_offset conflicts with bch ecc area.
> 
> The following graph is modified from kernel gpmi-nand.c driver with each
> data block 512 bytes.
> We can see that Block Mark conflicts with ecc area from bch view.
> We can enlarge the ecc chunk size to avoid this problem to those oobsize
> which is larger than 512.

What exactly is the impact of this patch for current installations of U-Boot?
Does the NAND need to be rewritten with new content? Is the format introduced
by this patch compatible with Linux?

Thanks!

Best regards,
Marek Vasut

  parent reply	other threads:[~2015-01-20 11:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-19  4:39 [U-Boot] [PATCH 1/2] mtd:mxs:nand calculate ecc strength dynamically Peng Fan
2014-12-19  4:39 ` [U-Boot] [PATCH 2/2] mtd:mxs:nand support oobsize bigger than 512 Peng Fan
2015-01-20  6:35   ` Peng Fan
2015-01-20 11:03   ` Marek Vasut [this message]
2015-01-20 13:12     ` Peng Fan
2015-01-22  7:09       ` Marek Vasut
2015-01-20  6:35 ` [U-Boot] [PATCH 1/2] mtd:mxs:nand calculate ecc strength dynamically Peng Fan
2015-01-20 11:04   ` Marek Vasut
2015-01-20 13:18     ` Peng Fan
2015-01-20 11:02 ` Marek Vasut
2015-01-27 23:14 ` Jörg Krause

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=201501201203.49418.marex@denx.de \
    --to=marex@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.