Kconfig 13 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301
  1. #
  2. # PARIDE configuration
  3. #
  4. # PARIDE doesn't need PARPORT, but if PARPORT is configured as a module,
  5. # PARIDE must also be a module.
  6. # PARIDE only supports PC style parports. Tough for USB or other parports...
  7. comment "Parallel IDE high-level drivers"
  8. depends on PARIDE
  9. config PARIDE_PD
  10. tristate "Parallel port IDE disks"
  11. depends on PARIDE
  12. help
  13. This option enables the high-level driver for IDE-type disk devices
  14. connected through a parallel port. If you chose to build PARIDE
  15. support into your kernel, you may answer Y here to build in the
  16. parallel port IDE driver, otherwise you should answer M to build
  17. it as a loadable module. The module will be called pd. You
  18. must also have at least one parallel port protocol driver in your
  19. system. Among the devices supported by this driver are the SyQuest
  20. EZ-135, EZ-230 and SparQ drives, the Avatar Shark and the backpack
  21. hard drives from MicroSolutions.
  22. config PARIDE_PCD
  23. tristate "Parallel port ATAPI CD-ROMs"
  24. depends on PARIDE
  25. ---help---
  26. This option enables the high-level driver for ATAPI CD-ROM devices
  27. connected through a parallel port. If you chose to build PARIDE
  28. support into your kernel, you may answer Y here to build in the
  29. parallel port ATAPI CD-ROM driver, otherwise you should answer M to
  30. build it as a loadable module. The module will be called pcd. You
  31. must also have at least one parallel port protocol driver in your
  32. system. Among the devices supported by this driver are the
  33. MicroSolutions backpack CD-ROM drives and the Freecom Power CD. If
  34. you have such a CD-ROM drive, you should also say Y or M to "ISO
  35. 9660 CD-ROM file system support" below, because that's the file
  36. system used on CD-ROMs.
  37. config PARIDE_PF
  38. tristate "Parallel port ATAPI disks"
  39. depends on PARIDE
  40. help
  41. This option enables the high-level driver for ATAPI disk devices
  42. connected through a parallel port. If you chose to build PARIDE
  43. support into your kernel, you may answer Y here to build in the
  44. parallel port ATAPI disk driver, otherwise you should answer M
  45. to build it as a loadable module. The module will be called pf.
  46. You must also have at least one parallel port protocol driver in
  47. your system. Among the devices supported by this driver are the
  48. MicroSolutions backpack PD/CD drive and the Imation Superdisk
  49. LS-120 drive.
  50. config PARIDE_PT
  51. tristate "Parallel port ATAPI tapes"
  52. depends on PARIDE
  53. help
  54. This option enables the high-level driver for ATAPI tape devices
  55. connected through a parallel port. If you chose to build PARIDE
  56. support into your kernel, you may answer Y here to build in the
  57. parallel port ATAPI disk driver, otherwise you should answer M
  58. to build it as a loadable module. The module will be called pt.
  59. You must also have at least one parallel port protocol driver in
  60. your system. Among the devices supported by this driver is the
  61. parallel port version of the HP 5GB drive.
  62. config PARIDE_PG
  63. tristate "Parallel port generic ATAPI devices"
  64. depends on PARIDE
  65. ---help---
  66. This option enables a special high-level driver for generic ATAPI
  67. devices connected through a parallel port. The driver allows user
  68. programs, such as cdrtools, to send ATAPI commands directly to a
  69. device.
  70. If you chose to build PARIDE support into your kernel, you may
  71. answer Y here to build in the parallel port generic ATAPI driver,
  72. otherwise you should answer M to build it as a loadable module. The
  73. module will be called pg.
  74. You must also have at least one parallel port protocol driver in
  75. your system.
  76. This driver implements an API loosely related to the generic SCSI
  77. driver. See <file:include/linux/pg.h>. for details.
  78. You can obtain the most recent version of cdrtools from
  79. <ftp://ftp.berlios.de/pub/cdrecord/>. Versions 1.6.1a3 and
  80. later fully support this driver.
  81. comment "Parallel IDE protocol modules"
  82. depends on PARIDE
  83. config PARIDE_ATEN
  84. tristate "ATEN EH-100 protocol"
  85. depends on PARIDE
  86. help
  87. This option enables support for the ATEN EH-100 parallel port IDE
  88. protocol. This protocol is used in some inexpensive low performance
  89. parallel port kits made in Hong Kong. If you chose to build PARIDE
  90. support into your kernel, you may answer Y here to build in the
  91. protocol driver, otherwise you should answer M to build it as a
  92. loadable module. The module will be called aten. You must also
  93. have a high-level driver for the type of device that you want to
  94. support.
  95. config PARIDE_BPCK
  96. tristate "MicroSolutions backpack (Series 5) protocol"
  97. depends on PARIDE
  98. ---help---
  99. This option enables support for the Micro Solutions BACKPACK
  100. parallel port Series 5 IDE protocol. (Most BACKPACK drives made
  101. before 1999 were Series 5) Series 5 drives will NOT always have the
  102. Series noted on the bottom of the drive. Series 6 drivers will.
  103. In other words, if your BACKPACK drive doesn't say "Series 6" on the
  104. bottom, enable this option.
  105. If you chose to build PARIDE support into your kernel, you may
  106. answer Y here to build in the protocol driver, otherwise you should
  107. answer M to build it as a loadable module. The module will be
  108. called bpck. You must also have a high-level driver for the type
  109. of device that you want to support.
  110. config PARIDE_BPCK6
  111. tristate "MicroSolutions backpack (Series 6) protocol"
  112. depends on PARIDE && !64BIT
  113. ---help---
  114. This option enables support for the Micro Solutions BACKPACK
  115. parallel port Series 6 IDE protocol. (Most BACKPACK drives made
  116. after 1999 were Series 6) Series 6 drives will have the Series noted
  117. on the bottom of the drive. Series 5 drivers don't always have it
  118. noted.
  119. In other words, if your BACKPACK drive says "Series 6" on the
  120. bottom, enable this option.
  121. If you chose to build PARIDE support into your kernel, you may
  122. answer Y here to build in the protocol driver, otherwise you should
  123. answer M to build it as a loadable module. The module will be
  124. called bpck6. You must also have a high-level driver for the type
  125. of device that you want to support.
  126. config PARIDE_COMM
  127. tristate "DataStor Commuter protocol"
  128. depends on PARIDE
  129. help
  130. This option enables support for the Commuter parallel port IDE
  131. protocol from DataStor. If you chose to build PARIDE support
  132. into your kernel, you may answer Y here to build in the protocol
  133. driver, otherwise you should answer M to build it as a loadable
  134. module. The module will be called comm. You must also have
  135. a high-level driver for the type of device that you want to support.
  136. config PARIDE_DSTR
  137. tristate "DataStor EP-2000 protocol"
  138. depends on PARIDE
  139. help
  140. This option enables support for the EP-2000 parallel port IDE
  141. protocol from DataStor. If you chose to build PARIDE support
  142. into your kernel, you may answer Y here to build in the protocol
  143. driver, otherwise you should answer M to build it as a loadable
  144. module. The module will be called dstr. You must also have
  145. a high-level driver for the type of device that you want to support.
  146. config PARIDE_FIT2
  147. tristate "FIT TD-2000 protocol"
  148. depends on PARIDE
  149. help
  150. This option enables support for the TD-2000 parallel port IDE
  151. protocol from Fidelity International Technology. This is a simple
  152. (low speed) adapter that is used in some portable hard drives. If
  153. you chose to build PARIDE support into your kernel, you may answer Y
  154. here to build in the protocol driver, otherwise you should answer M
  155. to build it as a loadable module. The module will be called ktti.
  156. You must also have a high-level driver for the type of device that
  157. you want to support.
  158. config PARIDE_FIT3
  159. tristate "FIT TD-3000 protocol"
  160. depends on PARIDE
  161. help
  162. This option enables support for the TD-3000 parallel port IDE
  163. protocol from Fidelity International Technology. This protocol is
  164. used in newer models of their portable disk, CD-ROM and PD/CD
  165. devices. If you chose to build PARIDE support into your kernel, you
  166. may answer Y here to build in the protocol driver, otherwise you
  167. should answer M to build it as a loadable module. The module will be
  168. called fit3. You must also have a high-level driver for the type
  169. of device that you want to support.
  170. config PARIDE_EPAT
  171. tristate "Shuttle EPAT/EPEZ protocol"
  172. depends on PARIDE
  173. help
  174. This option enables support for the EPAT parallel port IDE protocol.
  175. EPAT is a parallel port IDE adapter manufactured by Shuttle
  176. Technology and widely used in devices from major vendors such as
  177. Hewlett-Packard, SyQuest, Imation and Avatar. If you chose to build
  178. PARIDE support into your kernel, you may answer Y here to build in
  179. the protocol driver, otherwise you should answer M to build it as a
  180. loadable module. The module will be called epat. You must also
  181. have a high-level driver for the type of device that you want to
  182. support.
  183. config PARIDE_EPATC8
  184. bool "Support c7/c8 chips"
  185. depends on PARIDE_EPAT
  186. help
  187. This option enables support for the newer Shuttle EP1284 (aka c7 and
  188. c8) chip. You need this if you are using any recent Imation SuperDisk
  189. (LS-120) drive.
  190. config PARIDE_EPIA
  191. tristate "Shuttle EPIA protocol"
  192. depends on PARIDE
  193. help
  194. This option enables support for the (obsolete) EPIA parallel port
  195. IDE protocol from Shuttle Technology. This adapter can still be
  196. found in some no-name kits. If you chose to build PARIDE support
  197. into your kernel, you may answer Y here to build in the protocol
  198. driver, otherwise you should answer M to build it as a loadable
  199. module. The module will be called epia. You must also have a
  200. high-level driver for the type of device that you want to support.
  201. config PARIDE_FRIQ
  202. tristate "Freecom IQ ASIC-2 protocol"
  203. depends on PARIDE
  204. help
  205. This option enables support for version 2 of the Freecom IQ parallel
  206. port IDE adapter. This adapter is used by the Maxell Superdisk
  207. drive. If you chose to build PARIDE support into your kernel, you
  208. may answer Y here to build in the protocol driver, otherwise you
  209. should answer M to build it as a loadable module. The module will be
  210. called friq. You must also have a high-level driver for the type
  211. of device that you want to support.
  212. config PARIDE_FRPW
  213. tristate "FreeCom power protocol"
  214. depends on PARIDE
  215. help
  216. This option enables support for the Freecom power parallel port IDE
  217. protocol. If you chose to build PARIDE support into your kernel, you
  218. may answer Y here to build in the protocol driver, otherwise you
  219. should answer M to build it as a loadable module. The module will be
  220. called frpw. You must also have a high-level driver for the type
  221. of device that you want to support.
  222. config PARIDE_KBIC
  223. tristate "KingByte KBIC-951A/971A protocols"
  224. depends on PARIDE
  225. help
  226. This option enables support for the KBIC-951A and KBIC-971A parallel
  227. port IDE protocols from KingByte Information Corp. KingByte's
  228. adapters appear in many no-name portable disk and CD-ROM products,
  229. especially in Europe. If you chose to build PARIDE support into your
  230. kernel, you may answer Y here to build in the protocol driver,
  231. otherwise you should answer M to build it as a loadable module. The
  232. module will be called kbic. You must also have a high-level driver
  233. for the type of device that you want to support.
  234. config PARIDE_KTTI
  235. tristate "KT PHd protocol"
  236. depends on PARIDE
  237. help
  238. This option enables support for the "PHd" parallel port IDE protocol
  239. from KT Technology. This is a simple (low speed) adapter that is
  240. used in some 2.5" portable hard drives. If you chose to build PARIDE
  241. support into your kernel, you may answer Y here to build in the
  242. protocol driver, otherwise you should answer M to build it as a
  243. loadable module. The module will be called ktti. You must also
  244. have a high-level driver for the type of device that you want to
  245. support.
  246. config PARIDE_ON20
  247. tristate "OnSpec 90c20 protocol"
  248. depends on PARIDE
  249. help
  250. This option enables support for the (obsolete) 90c20 parallel port
  251. IDE protocol from OnSpec (often marketed under the ValuStore brand
  252. name). If you chose to build PARIDE support into your kernel, you
  253. may answer Y here to build in the protocol driver, otherwise you
  254. should answer M to build it as a loadable module. The module will
  255. be called on20. You must also have a high-level driver for the
  256. type of device that you want to support.
  257. config PARIDE_ON26
  258. tristate "OnSpec 90c26 protocol"
  259. depends on PARIDE
  260. help
  261. This option enables support for the 90c26 parallel port IDE protocol
  262. from OnSpec Electronics (often marketed under the ValuStore brand
  263. name). If you chose to build PARIDE support into your kernel, you
  264. may answer Y here to build in the protocol driver, otherwise you
  265. should answer M to build it as a loadable module. The module will be
  266. called on26. You must also have a high-level driver for the type
  267. of device that you want to support.
  268. #