diff options
author | Adrian Schmutzler <freifunk@adrianschmutzler.de> | 2020-12-27 20:33:57 +0100 |
---|---|---|
committer | Adrian Schmutzler <freifunk@adrianschmutzler.de> | 2020-12-27 20:33:57 +0100 |
commit | 9d96b6fb720d9cecc7bd50b4f16dabe1b337f9f2 (patch) | |
tree | ad53ca3fdf54309ef4537fff3ae3d00f647a0483 /target/linux/bcm63xx/patches-5.4/342-MIPS-BCM63XX-split-PCIe-reset-signals.patch | |
parent | 1fb40a72da115073b55ed1b92b443c1b80794c44 (diff) | |
download | upstream-9d96b6fb720d9cecc7bd50b4f16dabe1b337f9f2.tar.gz upstream-9d96b6fb720d9cecc7bd50b4f16dabe1b337f9f2.tar.bz2 upstream-9d96b6fb720d9cecc7bd50b4f16dabe1b337f9f2.zip |
ath79/mikrotik: disable building NAND images
The current support for MikroTik NAND-based devices relies on a
gross hack that packs the kernel into a static YAFFS stub, as the
stock bootloader only supports booting a YAFFS-encapsulated kernel.
The problem with this approach is that since the kernel partition is
blindly overwritten without any kind of wear or badblock management
(due to lack of proper support for YAFFS in OpenWRT), the NAND flash
is not worn uniformly and eventually badblocks appear, leading to
unbootable devices.
This issue has been reported here [1] and discussed in more detail
here [2].
[1] https://forum.openwrt.org/t/rb433-bad-sector-cannot-start-openwrt/71519
[2] https://github.com/openwrt/openwrt/pull/3026#issuecomment-673597461
Until a proper fix is found (or the stock bootloader supports other
filesystems), we disable building these images to prevent unknowing
users from risking their devices.
Thanks to Thibaut Varène for summarizing the details above.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Diffstat (limited to 'target/linux/bcm63xx/patches-5.4/342-MIPS-BCM63XX-split-PCIe-reset-signals.patch')
0 files changed, 0 insertions, 0 deletions