aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/realtek/patches-5.4/301-gpio-add-rtl838x-driver.patch
diff options
context:
space:
mode:
authorDaniel Golle <daniel@makrotopia.org>2022-02-17 15:10:00 +0000
committerDaniel Golle <daniel@makrotopia.org>2022-02-17 15:15:42 +0000
commit397de500896f3c7c4e2468c21521502392af4574 (patch)
tree054af1102430ef3b23c638bdb1bffcf210fbc566 /target/linux/realtek/patches-5.4/301-gpio-add-rtl838x-driver.patch
parentadd7884cd09a828467a8ad88c7c5e719f2c77410 (diff)
downloadupstream-397de500896f3c7c4e2468c21521502392af4574.tar.gz
upstream-397de500896f3c7c4e2468c21521502392af4574.tar.bz2
upstream-397de500896f3c7c4e2468c21521502392af4574.zip
base-files: Make sure rootfs_data_max is considered
For sysupgrade on NAND/UBI devices there is the U-Boot environment variable rootfs_data_max which can be used to limit the size of the rootfs_data volume created on sysupgrade. This stopped working reliable with recent kernels, probably due to a race condition when reading the number of free erase blocks from sysfs just after removing a volume. Change the script to just try creating rootfs_data with the desired size and retry with maximum size in case that fails. Hence calculating the available size in the script can be dropped which works around the problem. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
Diffstat (limited to 'target/linux/realtek/patches-5.4/301-gpio-add-rtl838x-driver.patch')
0 files changed, 0 insertions, 0 deletions