aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/mvebu/files
diff options
context:
space:
mode:
authorEnrico Mioso <mrkiko.rs@gmail.com>2022-02-10 14:35:49 +0100
committerChristian Lamparter <chunkeey@gmail.com>2022-02-19 18:29:42 +0100
commit22436d762bbd872c347a7b1ef21c474625435ff8 (patch)
tree8cdc701ba4d9341b72839789d3cd4b4bb734ba45 /target/linux/mvebu/files
parentc5dca805267eacc2c6f0ced2ea80d46846834360 (diff)
downloadupstream-22436d762bbd872c347a7b1ef21c474625435ff8.tar.gz
upstream-22436d762bbd872c347a7b1ef21c474625435ff8.tar.bz2
upstream-22436d762bbd872c347a7b1ef21c474625435ff8.zip
mvebu: mark all mtd partitions on GL.iNet GL-MV1000 read-only
On this device, two of the three defined MTD partitions are 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.rs@gmail.com>
Diffstat (limited to 'target/linux/mvebu/files')
-rw-r--r--target/linux/mvebu/files/arch/arm64/boot/dts/marvell/armada-3720-gl-mv1000.dts3
1 files changed, 3 insertions, 0 deletions
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;
};
};
};