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