1*4882a593Smuzhiyunconfig BR2_TARGET_ROOTFS_CRAMFS 2*4882a593Smuzhiyun bool "cramfs root filesystem" 3*4882a593Smuzhiyun help 4*4882a593Smuzhiyun Build a cramfs root filesystem 5*4882a593Smuzhiyun 6*4882a593Smuzhiyun https://github.com/npitre/cramfs-tools 7*4882a593Smuzhiyun 8*4882a593Smuzhiyunif BR2_TARGET_ROOTFS_CRAMFS 9*4882a593Smuzhiyun 10*4882a593Smuzhiyunconfig BR2_TARGET_ROOTFS_CRAMFS_XIP 11*4882a593Smuzhiyun bool "Support XIP of all ELF files" 12*4882a593Smuzhiyun help 13*4882a593Smuzhiyun For ELF files, uncompressed and properly aligned data blocks 14*4882a593Smuzhiyun will be automatically be mapped directly into user space 15*4882a593Smuzhiyun whenever possible providing eXecute-In-Place (XIP) from ROM 16*4882a593Smuzhiyun of read-only segments. Data segments mapped read-write 17*4882a593Smuzhiyun (hence they have to be copied to RAM) may still be 18*4882a593Smuzhiyun compressed in the cramfs image in the same file along with 19*4882a593Smuzhiyun non compressed read-only segments. Both MMU and no-MMU 20*4882a593Smuzhiyun systems are supported. This is particularly handy for tiny 21*4882a593Smuzhiyun embedded systems with very tight memory constraints. 22*4882a593Smuzhiyun 23*4882a593Smuzhiyun The CRAMFS_MTD Kconfig option must also be enabled in a 24*4882a593Smuzhiyun 4.15+ kernel. 25*4882a593Smuzhiyun 26*4882a593Smuzhiyunendif # BR2_TARGET_ROOTFS_CRAMFS 27