| Alexey Dobriyan | 4181024 | 2009-01-22 11:03:34 +0300 | [diff] [blame] | 1 | config ROMFS_FS |
| 2 | tristate "ROM file system support" |
| 3 | depends on BLOCK |
| 4 | ---help--- |
| 5 | This is a very small read-only file system mainly intended for |
| 6 | initial ram disks of installation disks, but it could be used for |
| 7 | other read-only media as well. Read |
| 8 | <file:Documentation/filesystems/romfs.txt> for details. |
| 9 | |
| 10 | To compile this file system support as a module, choose M here: the |
| 11 | module will be called romfs. Note that the file system of your |
| 12 | root partition (the one containing the directory /) cannot be a |
| 13 | module. |
| 14 | |
| 15 | If you don't know whether you need it, then you don't need it: |
| 16 | answer N. |
| David Howells | da4458b | 2009-02-12 10:40:10 +0000 | [diff] [blame^] | 17 | |
| 18 | config ROMFS_ON_BLOCK |
| 19 | bool "Block device-backed ROM file system support" if (ROMFS_ON_MTD && EMBEDDED) |
| 20 | depends on ROMFS_FS && BLOCK |
| 21 | help |
| 22 | This permits ROMFS to use block devices buffered through the page |
| 23 | cache as the medium from which to retrieve data. It does not allow |
| 24 | direct mapping of the medium. |
| 25 | |
| 26 | If unsure, answer Y. |
| 27 | |
| 28 | config ROMFS_ON_MTD |
| 29 | bool "MTD-backed ROM file system support" |
| 30 | depends on ROMFS_FS |
| 31 | depends on MTD=y || (ROMFS_FS=m && MTD) |
| 32 | help |
| 33 | This permits ROMFS to use MTD based devices directly, without the |
| 34 | intercession of the block layer (which may have been disabled). It |
| 35 | also allows direct mapping of MTD devices through romfs files under |
| 36 | NOMMU conditions if the underlying device is directly addressable by |
| 37 | the CPU. |
| 38 | |
| 39 | If unsure, answer Y. |
| 40 | |