aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/ramips/dts/TL-WR840NV5.dts
diff options
context:
space:
mode:
authorSerg Studzinskii <serguzhg@gmail.com>2017-12-24 18:00:13 +0200
committerJohn Crispin <john@phrozen.org>2018-01-18 08:04:18 +0100
commiteb58b14d27e089d345a66fd8e8c2df995fcac8be (patch)
treeca0b4fa106d4f10ca38cb41bb7c7cbc9038e3e18 /target/linux/ramips/dts/TL-WR840NV5.dts
parent4343ac5515569e564919e6e828246bf6d8663734 (diff)
downloadupstream-eb58b14d27e089d345a66fd8e8c2df995fcac8be.tar.gz
upstream-eb58b14d27e089d345a66fd8e8c2df995fcac8be.tar.bz2
upstream-eb58b14d27e089d345a66fd8e8c2df995fcac8be.zip
ramips: tl-wr840n-v5: increase firmware partition for 4Mmtk layot
According to console log during TP-Link TL-WR840N v5 OEM firmware update procedure 0x3e0000-0x3f0000 64kB "config" partition, which is used to store router's configuration settings, is erased and recreated again during every OEM firmware update procedure, thus does not contain any valuable factory data. So it is conviniant to use this extra 64kB erase block for jffs overlay due limited flash size on this device like it used on TP-Link's ar71xx boards. Signed-off-by: Serg Studzinskii <serguzhg@gmail.com>
Diffstat (limited to 'target/linux/ramips/dts/TL-WR840NV5.dts')
-rw-r--r--target/linux/ramips/dts/TL-WR840NV5.dts8
1 files changed, 1 insertions, 7 deletions
diff --git a/target/linux/ramips/dts/TL-WR840NV5.dts b/target/linux/ramips/dts/TL-WR840NV5.dts
index 340f2bbd83..ecc0fedd59 100644
--- a/target/linux/ramips/dts/TL-WR840NV5.dts
+++ b/target/linux/ramips/dts/TL-WR840NV5.dts
@@ -65,13 +65,7 @@
partition@20000 {
label = "firmware";
- reg = <0x20000 0x3c0000>;
- };
-
- partition@3e0000 {
- label = "config";
- reg = <0x3e0000 0x10000>;
- read-only;
+ reg = <0x20000 0x3d0000>;
};
factory: partition@3f0000 {