aboutsummaryrefslogtreecommitdiff
path: root/fs/cramfs/Config.in
blob: 89f8ad52b8aba4b03adc4cb485d0c86eb423cea2 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
config BR2_TARGET_ROOTFS_CRAMFS
	bool "cramfs root filesystem"
	help
	  Build a cramfs root filesystem

	  https://github.com/npitre/cramfs-tools

if BR2_TARGET_ROOTFS_CRAMFS

config BR2_TARGET_ROOTFS_CRAMFS_XIP
	bool "Support XIP of all ELF files"
	help
	  For ELF files, uncompressed and properly aligned data blocks
	  will be automatically be mapped directly into user space
	  whenever possible providing eXecute-In-Place (XIP) from ROM
	  of read-only segments. Data segments mapped read-write
	  (hence they have to be copied to RAM) may still be
	  compressed in the cramfs image in the same file along with
	  non compressed read-only segments. Both MMU and no-MMU
	  systems are supported. This is particularly handy for tiny
	  embedded systems with very tight memory constraints.

	  The CRAMFS_MTD Kconfig option must also be enabled in a
	  4.15+ kernel.

endif # BR2_TARGET_ROOTFS_CRAMFS