diff options
author | Koen Vandeputte <koen.vandeputte@ncentric.com> | 2018-10-18 14:23:36 +0200 |
---|---|---|
committer | Koen Vandeputte <koen.vandeputte@ncentric.com> | 2018-10-29 10:56:59 +0100 |
commit | f1a2b5bbbc46084b64c36f2b665a60f2317bddc0 (patch) | |
tree | 8f96110df785655ad32834aa0d6ee499d98a71f8 /target/linux/oxnas/patches-4.14 | |
parent | 24ca1cda38fbc3c5ae1302e44ea9dba20cf01ea0 (diff) | |
download | upstream-f1a2b5bbbc46084b64c36f2b665a60f2317bddc0.tar.gz upstream-f1a2b5bbbc46084b64c36f2b665a60f2317bddc0.tar.bz2 upstream-f1a2b5bbbc46084b64c36f2b665a60f2317bddc0.zip |
kernel: tolerate using UBI/UBIFS on MLC flash (FS#1830)
starting from upstream commit 577b4eb23811 ("ubi: Reject MLC NAND")
it is not allowed to use UBI and UBIFS on a MLC flavoured NAND flash chip. [1]
According to David Oberhollenzer [2]:
The real problem is that on MLC NAND, pages come in pairs.
Multiple voltage levels inside a single, physical memory cell are used to
encode more than one bit. Instead of just having pages that are twice as big,
the flash exposes them as two different pages. Those pages are usually not
ordered sequentially either, but according to a vendor/device specific
pairing scheme.
Within OpenWrt, devices utilizing this type of flash,
combined with UBI(fs) will be bricked when a user upgrades
from 17.01.4 to a newer version as the MLC will be refused.
As these devices are currently advertised as supported by OpenWrt,
we should at least maintain the original state during the lifecycle
of the current releases.
Support can be gracefully ended when a new release-branch is created.
Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
Acked-by: Hauke Mehrtens <hauke@hauke-m.e>
[1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v4.14.77&id=577b4eb23811dfc8e38924dc476dbc866be74253
[2] https://lore.kernel.org/patchwork/patch/920344/
Diffstat (limited to 'target/linux/oxnas/patches-4.14')
0 files changed, 0 insertions, 0 deletions