From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marek Vasut Date: Tue, 20 Jan 2015 12:03:49 +0100 Subject: [U-Boot] [PATCH 2/2] mtd:mxs:nand support oobsize bigger than 512 In-Reply-To: <1418963953-1623-2-git-send-email-Peng.Fan@freescale.com> References: <1418963953-1623-1-git-send-email-Peng.Fan@freescale.com> <1418963953-1623-2-git-send-email-Peng.Fan@freescale.com> Message-ID: <201501201203.49418.marex@denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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