Kconfig 13 KB

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