diff options
author | Daniel Golle <daniel@makrotopia.org> | 2021-02-17 15:17:49 +0000 |
---|---|---|
committer | Daniel Golle <daniel@makrotopia.org> | 2021-02-24 01:35:20 +0000 |
commit | 5c10f26c28031c0d7e72b672623727adb5df7b2d (patch) | |
tree | 2362cacb0e64046c32ae10261475b63912a49cc8 /toolchain/gcc/common.mk | |
parent | 330bd380e8b691833c8dcc9b579b51851cbd4b0f (diff) | |
download | upstream-5c10f26c28031c0d7e72b672623727adb5df7b2d.tar.gz upstream-5c10f26c28031c0d7e72b672623727adb5df7b2d.tar.bz2 upstream-5c10f26c28031c0d7e72b672623727adb5df7b2d.zip |
sysupgrade-nand: allow limiting rootfs_data by setting env variable
Check if firmware environment variable 'rootfs_data_max' exists and is
set to a numerical value greater than 0. If so, limit rootfs_data
volume to that size instead of using the maximum available size.
This is useful on devices with lots of flash where users may want to
have eg. a volume for persistent logs and statistics or for external
applications/containers. Persistence on rootfs overlay is limited by
the size of memory available during the sysugprade process as that
data needs to be copied to RAM while the volume is being recreated
during sysupgrade. Hence it is unsuitable for keeping larger amounts
of data accross upgrade which makes additional volume(s) for
application data desirable.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
Diffstat (limited to 'toolchain/gcc/common.mk')
0 files changed, 0 insertions, 0 deletions