aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/omap24xx
diff options
context:
space:
mode:
authorChristian Lamparter <chunkeey@gmail.com>2018-07-29 11:55:15 +0200
committerJohn Crispin <john@phrozen.org>2018-07-30 08:11:56 +0200
commitaed4799d6d05d89dbca1bd5f14cc3d09ac563f3b (patch)
treee25dae8904f5ae669c619e623bc854666fe5e0de /target/linux/omap24xx
parent7516a960113d512cb2909f40bd07caf2a6c547b1 (diff)
downloadupstream-aed4799d6d05d89dbca1bd5f14cc3d09ac563f3b.tar.gz
upstream-aed4799d6d05d89dbca1bd5f14cc3d09ac563f3b.tar.bz2
upstream-aed4799d6d05d89dbca1bd5f14cc3d09ac563f3b.zip
apm821xx: build squashfs-rootfs images for the MBL
This patch adds support for squashfs as the root filesystem. advantages: - migrate from a existing -ext4 installation and back with the sysupgrade utility - existing partition layout will not be lost during switch - slightly smaller image size as compared to the -ext4 image. disadvantages: - needs f2fs + tools. This is because fstools rootdisk.c decides based on the partition size (currently root partitions > 100 MiB) f2fs is used as the rootfs_data filesystem. - rootfs_data is placed into the rootfs partition after the squashfs. This makes it difficult for tools that expect a /dev/sda${X} device. It also makes it difficult for data recovery tools as they might not expect to find a embedded partition or will be slightly confused. ... or will not support f2fs. For people with existing build configurations: make sure to include mkf2fs and f2fsck packages into the image. Otherwise the new -squashfs image will only boot from the ram-overlay. Note: All overlay data (configurations/all installed packages/...) will be placed in inside the rootfs partition (i.e. /dev/sda2) just after the squashfs image. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
Diffstat (limited to 'target/linux/omap24xx')
0 files changed, 0 insertions, 0 deletions