Kconfig 1.4 KB

12345678910111213141516171819202122232425262728293031323334353637383940
  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. To compile this file system support as a module, choose M here: the
  10. module will be called romfs. Note that the file system of your
  11. root partition (the one containing the directory /) cannot be a
  12. module.
  13. If you don't know whether you need it, then you don't need it:
  14. answer N.
  15. config ROMFS_ON_BLOCK
  16. bool "Block device-backed ROM file system support" if (ROMFS_ON_MTD && EMBEDDED)
  17. depends on ROMFS_FS && BLOCK
  18. help
  19. This permits ROMFS to use block devices buffered through the page
  20. cache as the medium from which to retrieve data. It does not allow
  21. direct mapping of the medium.
  22. If unsure, answer Y.
  23. config ROMFS_ON_MTD
  24. bool "MTD-backed ROM file system support"
  25. depends on ROMFS_FS
  26. depends on MTD=y || (ROMFS_FS=m && MTD)
  27. help
  28. This permits ROMFS to use MTD based devices directly, without the
  29. intercession of the block layer (which may have been disabled). It
  30. also allows direct mapping of MTD devices through romfs files under
  31. NOMMU conditions if the underlying device is directly addressable by
  32. the CPU.
  33. If unsure, answer Y.