| Kconfig (ce8ee02d519ab20c5b87d3b3929b5e44ad89e26f) | Kconfig (a8c6db00bff2bdb466d80b7ec7ff25d327071f9b) |
|---|---|
| 1config CRAMFS 2 tristate "Compressed ROM file system support (cramfs)" 3 select ZLIB_INFLATE 4 help 5 Saying Y here includes support for CramFs (Compressed ROM File 6 System). CramFs is designed to be a simple, small, and compressed 7 file system for ROM based embedded systems. CramFs is read-only, 8 limited to 256MB file systems (with 16MB files), and doesn't support --- 19 unchanged lines hidden (view full) --- 28 depends on CRAMFS && BLOCK 29 default y 30 help 31 This option allows the CramFs driver to load data from a regular 32 block device such a disk partition or a ramdisk. 33 34config CRAMFS_MTD 35 bool "Support CramFs image directly mapped in physical memory" | 1config CRAMFS 2 tristate "Compressed ROM file system support (cramfs)" 3 select ZLIB_INFLATE 4 help 5 Saying Y here includes support for CramFs (Compressed ROM File 6 System). CramFs is designed to be a simple, small, and compressed 7 file system for ROM based embedded systems. CramFs is read-only, 8 limited to 256MB file systems (with 16MB files), and doesn't support --- 19 unchanged lines hidden (view full) --- 28 depends on CRAMFS && BLOCK 29 default y 30 help 31 This option allows the CramFs driver to load data from a regular 32 block device such a disk partition or a ramdisk. 33 34config CRAMFS_MTD 35 bool "Support CramFs image directly mapped in physical memory" |
| 36 depends on CRAMFS && MTD 37 depends on CRAMFS=m || MTD=y | 36 depends on CRAMFS && CRAMFS <= MTD |
| 38 default y if !CRAMFS_BLOCKDEV 39 help 40 This option allows the CramFs driver to load data directly from 41 a linear adressed memory range (usually non volatile memory 42 like flash) instead of going through the block device layer. 43 This saves some memory since no intermediate buffering is 44 necessary. 45 46 The location of the CramFs image is determined by a 47 MTD device capable of direct memory mapping e.g. from 48 the 'physmap' map driver or a resulting MTD partition. 49 For example, this would mount the cramfs image stored in 50 the MTD partition named "xip_fs" on the /mnt mountpoint: 51 52 mount -t cramfs mtd:xip_fs /mnt 53 54 If unsure, say N. | 37 default y if !CRAMFS_BLOCKDEV 38 help 39 This option allows the CramFs driver to load data directly from 40 a linear adressed memory range (usually non volatile memory 41 like flash) instead of going through the block device layer. 42 This saves some memory since no intermediate buffering is 43 necessary. 44 45 The location of the CramFs image is determined by a 46 MTD device capable of direct memory mapping e.g. from 47 the 'physmap' map driver or a resulting MTD partition. 48 For example, this would mount the cramfs image stored in 49 the MTD partition named "xip_fs" on the /mnt mountpoint: 50 51 mount -t cramfs mtd:xip_fs /mnt 52 53 If unsure, say N. |