Kconfig 2.0 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768
  1. if ARCH_S390
  2. comment "S/390 block device drivers"
  3. depends on ARCH_S390
  4. config BLK_DEV_XPRAM
  5. tristate "XPRAM disk support"
  6. depends on ARCH_S390
  7. help
  8. Select this option if you want to use your expanded storage on S/390
  9. or zSeries as a disk. This is useful as a _fast_ swap device if you
  10. want to access more than 2G of memory when running in 31 bit mode.
  11. This option is also available as a module which will be called
  12. xpram. If unsure, say "N".
  13. config DCSSBLK
  14. tristate "DCSSBLK support"
  15. help
  16. Support for dcss block device
  17. config DASD
  18. tristate "Support for DASD devices"
  19. depends on CCW
  20. help
  21. Enable this option if you want to access DASDs directly utilizing
  22. S/390s channel subsystem commands. This is necessary for running
  23. natively on a single image or an LPAR.
  24. config DASD_PROFILE
  25. bool "Profiling support for dasd devices"
  26. depends on DASD
  27. help
  28. Enable this option if you want to see profiling information
  29. in /proc/dasd/statistics.
  30. config DASD_ECKD
  31. tristate "Support for ECKD Disks"
  32. depends on DASD
  33. help
  34. ECKD devices are the most commonly used devices. You should enable
  35. this option unless you are very sure to have no ECKD device.
  36. config DASD_FBA
  37. tristate "Support for FBA Disks"
  38. depends on DASD
  39. help
  40. Select this option to be able to access FBA devices. It is safe to
  41. say "Y".
  42. config DASD_DIAG
  43. tristate "Support for DIAG access to Disks"
  44. depends on DASD && ( ARCH_S390X = 'n' || EXPERIMENTAL)
  45. help
  46. Select this option if you want to use Diagnose250 command to access
  47. Disks under VM. If you are not running under VM or unsure what it is,
  48. say "N".
  49. config DASD_CMB
  50. tristate "Compatibility interface for DASD channel measurement blocks"
  51. depends on DASD
  52. help
  53. This driver provides an additional interface to the channel measurement
  54. facility, which is normally accessed though sysfs, with a set of
  55. ioctl functions specific to the dasd driver.
  56. This is only needed if you want to use applications written for
  57. linux-2.4 dasd channel measurement facility interface.
  58. endif