Kconfig (e5451c8f8330e03ad3cfa16048b4daf961af434f) Kconfig (99c18ce580c6cc6763e694b4ce320d7b226ab59b)
1config CRAMFS
2 tristate "Compressed ROM file system support (cramfs) (OBSOLETE)"
1config CRAMFS
2 tristate "Compressed ROM file system support (cramfs) (OBSOLETE)"
3 depends on BLOCK
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,
9 limited to 256MB file systems (with 16MB files), and doesn't support
10 16/32 bits uid/gid, hard links and timestamps.
11
12 See <file:Documentation/filesystems/cramfs.txt> and
13 <file:fs/cramfs/README> for further information.
14
15 To compile this as a module, choose M here: the module will be called
16 cramfs. Note that the root file system (the one containing the
17 directory /) cannot be compiled as a module.
18
19 This filesystem is obsoleted by SquashFS, which is much better
20 in terms of performance and features.
21
22 If unsure, say N.
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
9 16/32 bits uid/gid, hard links and timestamps.
10
11 See <file:Documentation/filesystems/cramfs.txt> and
12 <file:fs/cramfs/README> for further information.
13
14 To compile this as a module, choose M here: the module will be called
15 cramfs. Note that the root file system (the one containing the
16 directory /) cannot be compiled as a module.
17
18 This filesystem is obsoleted by SquashFS, which is much better
19 in terms of performance and features.
20
21 If unsure, say N.
22
23config CRAMFS_BLOCKDEV
24 bool "Support CramFs image over a regular block device" if EXPERT
25 depends on CRAMFS && BLOCK
26 default y
27 help
28 This option allows the CramFs driver to load data from a regular
29 block device such a disk partition or a ramdisk.
30
31config CRAMFS_MTD
32 bool "Support CramFs image directly mapped in physical memory"
33 depends on CRAMFS && MTD
34 default y if !CRAMFS_BLOCKDEV
35 help
36 This option allows the CramFs driver to load data directly from
37 a linear adressed memory range (usually non volatile memory
38 like flash) instead of going through the block device layer.
39 This saves some memory since no intermediate buffering is
40 necessary.
41
42 The location of the CramFs image is determined by a
43 MTD device capable of direct memory mapping e.g. from
44 the 'physmap' map driver or a resulting MTD partition.
45 For example, this would mount the cramfs image stored in
46 the MTD partition named "xip_fs" on the /mnt mountpoint:
47
48 mount -t cramfs mtd:xip_fs /mnt
49
50 If unsure, say N.