summaryrefslogtreecommitdiffstats
path: root/config/Config-images.in
diff options
context:
space:
mode:
authorDaniel Golle <daniel@makrotopia.org>2024-04-30 22:21:16 +0100
committerDaniel Golle <daniel@makrotopia.org>2024-05-02 14:58:31 +0100
commit918d81a3eac01be2309a54435e06f0a9d6c6f812 (patch)
tree2e4796024dec940112a20a6848bc8ab577787577 /config/Config-images.in
parent219018185e52a49b6a676a3591fe28406bb1a062 (diff)
downloadopenwrt-918d81a3eac01be2309a54435e06f0a9d6c6f812.tar.gz
openwrt-918d81a3eac01be2309a54435e06f0a9d6c6f812.tar.bz2
openwrt-918d81a3eac01be2309a54435e06f0a9d6c6f812.zip
mediatek: increase size of the sdcard image to 512 MiB
Increasing the size of the rootfs_data filesystem has become a ever repeating discussion and seems to be the most important thing for users of the MediaTek-based BananaPi boards. Using the whole remaining size of a microSD or the eMMC for rootfs_data doesn't make sense for many reasons, but neither does the current default of 104 MiB for the 'rootfs' partition size. Increase the 'rootfs' partition size to 448 MiB which will result in the sdcard image being exactly 512 MiB. Finding a microSD card smaller than 512 MiB and still working could anyway be difficult in 2024. That will allow users to install even bloatware written in Go or other space-hungry languages while still leaving most of the space unallocated for additional partitions or volumes to be used for persistent user data. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
Diffstat (limited to 'config/Config-images.in')
-rw-r--r--config/Config-images.in1
1 files changed, 1 insertions, 0 deletions
diff --git a/config/Config-images.in b/config/Config-images.in
index 6f2f926432..5222065b04 100644
--- a/config/Config-images.in
+++ b/config/Config-images.in
@@ -300,6 +300,7 @@ menu "Target Images"
config TARGET_ROOTFS_PARTSIZE
int "Root filesystem partition size (in MiB)"
depends on USES_ROOTFS_PART || TARGET_ROOTFS_EXT4FS
+ default 448 if TARGET_mediatek
default 104
help
Select the root filesystem partition size.