CONFIG_TARGET_ROOTFS_PARTSIZE: Limitations on the size of the image

Banana Pi Router design BPI-R4/BPI-R4 Pro(MT7988)
1

Hi, All!

I have already set CONFIG_TARGET_ROOTFS_PARTSIZE=1008 in my .config.

I am trying to generate an image with a lot of packages built-in. However I am having problems because it seems that a limit is reached and make just spits out an error then exits the build. In this, https://github.com/frank-w/openwrt/blob/R4Pro_4e/target/linux/mediatek/image/filogic.mk#L770, Makefile routine any one of the calls to check-size could fail which then terminates the build.

What is also interesting is why the OpenWRT version does not match up with what Banana Pi released. Please look at the argument passed to check-size in BPI-R4PRO-4E-OPENWRT-V24.10.0-Master-Devel/target/linux/mediatek/image/filogic.mk at main · BPI-SINOVOIP/BPI-R4PRO-4E-OPENWRT-V24.10.0-Master-Devel · GitHub and you will notice that the values differ, and they define CONFIG_TARGET_ROOTFS_PARTSIZE=448 in .config. So my questions are:

  1. Maybe it is not clear to me right now but why enforce such a small size in upstream OpenWRT upstream?
  2. Where are these values derived from? I am almost certain they are not arbitary, I mean to say, they are coming from somewhere right? For instance, is it mandated anywhere that initramfs-recovery.itb needs to be a certain size?
  3. Why is CONFIG_TARGET_ROOTFS_PARTSIZE so low to begin with? I thought this devices shipped with 8GB of eMMC?

Thanks,

- Bana

2

The partsize is afaik so small because all mist fit into ram as backup while sysupgrade to restpre after it.