| Kconfig (4b4193256c8d3bc3a5397b5cd9494c2ad386317d) | Kconfig (a1f46ff2ff88ab8cec64953422f207a81ff379f8) |
|---|---|
| 1# SPDX-License-Identifier: GPL-2.0-only 2config CRAMFS 3 tristate "Compressed ROM file system support (cramfs)" 4 select ZLIB_INFLATE 5 help 6 Saying Y here includes support for CramFs (Compressed ROM File 7 System). CramFs is designed to be a simple, small, and compressed 8 file system for ROM based embedded systems. CramFs is read-only, --- 24 unchanged lines hidden (view full) --- 33 block device such a disk partition or a ramdisk. 34 35config CRAMFS_MTD 36 bool "Support CramFs image directly mapped in physical memory" 37 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 | 1# SPDX-License-Identifier: GPL-2.0-only 2config CRAMFS 3 tristate "Compressed ROM file system support (cramfs)" 4 select ZLIB_INFLATE 5 help 6 Saying Y here includes support for CramFs (Compressed ROM File 7 System). CramFs is designed to be a simple, small, and compressed 8 file system for ROM based embedded systems. CramFs is read-only, --- 24 unchanged lines hidden (view full) --- 33 block device such a disk partition or a ramdisk. 34 35config CRAMFS_MTD 36 bool "Support CramFs image directly mapped in physical memory" 37 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 | 41 a linear addressed 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. | 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. |