aboutsummaryrefslogtreecommitdiffstats
path: root/sound
diff options
context:
space:
mode:
authorArtem Bityutskiy <Artem.Bityutskiy@nokia.com>2010-12-02 06:34:01 +0200
committerArtem Bityutskiy <Artem.Bityutskiy@nokia.com>2010-12-03 15:49:21 +0200
commit7ac760c2f78ddd8e1bd633767b01becfbbf96720 (patch)
tree424592684b1e91ba7189195b0c89abd2f68b515b /sound
parente8a7e48bb248a1196484d3f8afa53bded2b24e71 (diff)
downloadmrst-s0i3-test-7ac760c2f78ddd8e1bd633767b01becfbbf96720.tar.gz
mrst-s0i3-test-7ac760c2f78ddd8e1bd633767b01becfbbf96720.tar.xz
mrst-s0i3-test-7ac760c2f78ddd8e1bd633767b01becfbbf96720.zip
UBI: fix corrupted PEB detection for NOR flash
My new shiny code for corrupted PEB detection has NOR specific bug. We tread PEB as corrupted and preserve it, if 1. EC header is OK. 2. VID header is corrupted. 3. data area is not "all 0xFFs" In case of NOR we have 'nor_erase_prepare()' quirk, which invalidates the headers before erasing the PEB. And we invalidate first the VID header, and then the EC header. So if a power cut happens after we have invalidated the VID header, but before we have invalidated the EC header, we end up with a PEB which satisfies the above 3 conditions, and the scanning code will treat it as corrupted, and will print scary warnings, wrongly. This patch fixes the issue by firt invalidating the EC header, then invalidating the VID header. In case of power cut inbetween, we still just lose the EC header, and UBI can deal with this situation gracefully. Thanks to Anatolij Gustschin <agust@denx.de> for tracking this down. Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com> Reported-by: Anatolij Gustschin <agust@denx.de> Tested-by: Anatolij Gustschin <agust@denx.de>
Diffstat (limited to 'sound')
0 files changed, 0 insertions, 0 deletions