12a22783bSAlexey Dobriyanconfig CRAMFS 254886a71SMichael Opdenacker tristate "Compressed ROM file system support (cramfs) (OBSOLETE)" 32a22783bSAlexey Dobriyan select ZLIB_INFLATE 42a22783bSAlexey Dobriyan help 52a22783bSAlexey Dobriyan Saying Y here includes support for CramFs (Compressed ROM File 62a22783bSAlexey Dobriyan System). CramFs is designed to be a simple, small, and compressed 72a22783bSAlexey Dobriyan file system for ROM based embedded systems. CramFs is read-only, 82a22783bSAlexey Dobriyan limited to 256MB file systems (with 16MB files), and doesn't support 92a22783bSAlexey Dobriyan 16/32 bits uid/gid, hard links and timestamps. 102a22783bSAlexey Dobriyan 112a22783bSAlexey Dobriyan See <file:Documentation/filesystems/cramfs.txt> and 122a22783bSAlexey Dobriyan <file:fs/cramfs/README> for further information. 132a22783bSAlexey Dobriyan 142a22783bSAlexey Dobriyan To compile this as a module, choose M here: the module will be called 152a22783bSAlexey Dobriyan cramfs. Note that the root file system (the one containing the 162a22783bSAlexey Dobriyan directory /) cannot be compiled as a module. 172a22783bSAlexey Dobriyan 1854886a71SMichael Opdenacker This filesystem is obsoleted by SquashFS, which is much better 1954886a71SMichael Opdenacker in terms of performance and features. 2054886a71SMichael Opdenacker 212a22783bSAlexey Dobriyan If unsure, say N. 22*99c18ce5SNicolas Pitre 23*99c18ce5SNicolas Pitreconfig CRAMFS_BLOCKDEV 24*99c18ce5SNicolas Pitre bool "Support CramFs image over a regular block device" if EXPERT 25*99c18ce5SNicolas Pitre depends on CRAMFS && BLOCK 26*99c18ce5SNicolas Pitre default y 27*99c18ce5SNicolas Pitre help 28*99c18ce5SNicolas Pitre This option allows the CramFs driver to load data from a regular 29*99c18ce5SNicolas Pitre block device such a disk partition or a ramdisk. 30*99c18ce5SNicolas Pitre 31*99c18ce5SNicolas Pitreconfig CRAMFS_MTD 32*99c18ce5SNicolas Pitre bool "Support CramFs image directly mapped in physical memory" 33*99c18ce5SNicolas Pitre depends on CRAMFS && MTD 34*99c18ce5SNicolas Pitre default y if !CRAMFS_BLOCKDEV 35*99c18ce5SNicolas Pitre help 36*99c18ce5SNicolas Pitre This option allows the CramFs driver to load data directly from 37*99c18ce5SNicolas Pitre a linear adressed memory range (usually non volatile memory 38*99c18ce5SNicolas Pitre like flash) instead of going through the block device layer. 39*99c18ce5SNicolas Pitre This saves some memory since no intermediate buffering is 40*99c18ce5SNicolas Pitre necessary. 41*99c18ce5SNicolas Pitre 42*99c18ce5SNicolas Pitre The location of the CramFs image is determined by a 43*99c18ce5SNicolas Pitre MTD device capable of direct memory mapping e.g. from 44*99c18ce5SNicolas Pitre the 'physmap' map driver or a resulting MTD partition. 45*99c18ce5SNicolas Pitre For example, this would mount the cramfs image stored in 46*99c18ce5SNicolas Pitre the MTD partition named "xip_fs" on the /mnt mountpoint: 47*99c18ce5SNicolas Pitre 48*99c18ce5SNicolas Pitre mount -t cramfs mtd:xip_fs /mnt 49*99c18ce5SNicolas Pitre 50*99c18ce5SNicolas Pitre If unsure, say N. 51