Kconfig 13 KB

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