summaryrefslogtreecommitdiffstats
path: root/block
diff options
context:
space:
mode:
authorRoger Quadros <rogerq@ti.com>2014-08-25 16:15:33 -0700
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2014-09-17 09:04:02 -0700
commit6562c0cc805b391489e2f511983300e802864aea (patch)
tree84612eac36d9461493ad096f085677e4ab6de309 /block
parenta9d28db622269c29825f13c28bae0f587f77aada (diff)
downloadlinux-stable-6562c0cc805b391489e2f511983300e802864aea.tar.gz
linux-stable-6562c0cc805b391489e2f511983300e802864aea.tar.bz2
linux-stable-6562c0cc805b391489e2f511983300e802864aea.zip
mtd: nand: omap: Fix 1-bit Hamming code scheme, omap_calculate_ecc()
commit 40ddbf5069bd4e11447c0088fc75318e0aac53f0 upstream. commit 65b97cf6b8de introduced in v3.7 caused a regression by using a reversed CS_MASK thus causing omap_calculate_ecc to always fail. As the NAND base driver never checks for .calculate()'s return value, the zeroed ECC values are used as is without showing any error to the user. However, this won't work and the NAND device won't be guarded by any error code. Fix the issue by using the correct mask. Code was tested on omap3beagle using the following procedure - flash the primary bootloader (MLO) from the kernel to the first NAND partition using nandwrite. - boot the board from NAND. This utilizes OMAP ROM loader that relies on 1-bit Hamming code ECC. Fixes: 65b97cf6b8de (mtd: nand: omap2: handle nand on gpmc) Signed-off-by: Roger Quadros <rogerq@ti.com> Signed-off-by: Tony Lindgren <tony@atomide.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions