aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMathias Kresin <dev@kresin.me>2017-10-19 23:11:59 +0200
committerMathias Kresin <dev@kresin.me>2017-12-11 10:31:00 +0100
commit0c7ad4e5d390a708bbc76b6cb9048460d52c08f1 (patch)
tree593cde0a9fe7e7615c93740b39ccfce1cd937094
parent893a1ede2eace247878eaa278d7bcda55cb54b8a (diff)
downloadupstream-0c7ad4e5d390a708bbc76b6cb9048460d52c08f1.tar.gz
upstream-0c7ad4e5d390a708bbc76b6cb9048460d52c08f1.tar.bz2
upstream-0c7ad4e5d390a708bbc76b6cb9048460d52c08f1.zip
lantiq: nand: drop ubifs images
Users are confused which image type they should use and there are more drawbacks than adavantages in using a r/w ubifs rootfs in constrast to a read-only squashfs rootfs like: - less available free flash space due to better compression of squashfs images - no support for factory reset due to r/w filesystem - possibility to break failsafe due to r/w filesystem Therefore, drop support for r/w ubifs rootfs images. Signed-off-by: Mathias Kresin <dev@kresin.me>
-rw-r--r--target/linux/lantiq/xrx200/target.mk2
-rw-r--r--target/linux/lantiq/xway/target.mk2
2 files changed, 2 insertions, 2 deletions
diff --git a/target/linux/lantiq/xrx200/target.mk b/target/linux/lantiq/xrx200/target.mk
index 9600f04fd2..fc8115e795 100644
--- a/target/linux/lantiq/xrx200/target.mk
+++ b/target/linux/lantiq/xrx200/target.mk
@@ -1,7 +1,7 @@
ARCH:=mips
SUBTARGET:=xrx200
BOARDNAME:=XRX200
-FEATURES:=squashfs atm nand ubifs
+FEATURES:=squashfs atm nand
CPU_TYPE:=24kc
DEFAULT_PACKAGES+=kmod-leds-gpio \
diff --git a/target/linux/lantiq/xway/target.mk b/target/linux/lantiq/xway/target.mk
index 429be761c4..550c61edf0 100644
--- a/target/linux/lantiq/xway/target.mk
+++ b/target/linux/lantiq/xway/target.mk
@@ -1,7 +1,7 @@
ARCH:=mips
SUBTARGET:=xway
BOARDNAME:=XWAY
-FEATURES:=squashfs atm nand ubifs ramdisk
+FEATURES:=squashfs atm nand ramdisk
CPU_TYPE:=24kc
DEFAULT_PACKAGES+=kmod-leds-gpio kmod-gpio-button-hotplug swconfig