On this device, two of the three defined MTD partitions arre
automatically set to read-only, since they do not end at an erase/write
block boundary.
In particular, the only partition remaining writable is the one holding
the u-boot bootloader.
Mark all of the partitions read-only, at least until a better
understanding of why the layout has been laid out this way is gained.
Signed-off-by: Enrico Mioso <mrkiko...@gmail.com>
---
.../arch/arm64/boot/dts/marvell/armada-3720-gl-mv1000.dts | 3 +++
1 file changed, 3 insertions(+)
diff --git
a/target/linux/mvebu/files/arch/arm64/boot/dts/marvell/armada-3720-gl-mv1000.dts
b/target/linux/mvebu/files/arch/arm64/boot/dts/marvell/armada-3720-gl-mv1000.dts
index cdc91880ee..acf15e8ca9 100644
---
a/target/linux/mvebu/files/arch/arm64/boot/dts/marvell/armada-3720-gl-mv1000.dts
+++
b/target/linux/mvebu/files/arch/arm64/boot/dts/marvell/armada-3720-gl-mv1000.dts
@@ -91,16 +91,19 @@
partition@0 {
label = "u-boot";
reg = <0 0xf0000>;
+ read-only;
};
partition@f0000 {
label = "u-boot-env";
reg = <0Xf0000 0x8000>;
+ read-only;
};
factory: partition@f8000 {
label = "factory";
reg = <0xf8000 0x8000>;
+ read-only;
};
};
};
--
2.35.1
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
