1 # SPDX-License-Identifier: GPL-2.0
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...
9 comment "Parallel IDE high-level drivers"
13 tristate "Parallel port IDE disks"
16 This option enables the high-level driver for IDE-type disk devices
17 connected through a parallel port. If you chose to build PARIDE
18 support into your kernel, you may answer Y here to build in the
19 parallel port IDE driver, otherwise you should answer M to build
20 it as a loadable module. The module will be called pd. You
21 must also have at least one parallel port protocol driver in your
22 system. Among the devices supported by this driver are the SyQuest
23 EZ-135, EZ-230 and SparQ drives, the Avatar Shark and the backpack
24 hard drives from MicroSolutions.
27 tristate "Parallel port ATAPI CD-ROMs"
31 This option enables the high-level driver for ATAPI CD-ROM devices
32 connected through a parallel port. If you chose to build PARIDE
33 support into your kernel, you may answer Y here to build in the
34 parallel port ATAPI CD-ROM driver, otherwise you should answer M to
35 build it as a loadable module. The module will be called pcd. You
36 must also have at least one parallel port protocol driver in your
37 system. Among the devices supported by this driver are the
38 MicroSolutions backpack CD-ROM drives and the Freecom Power CD. If
39 you have such a CD-ROM drive, you should also say Y or M to "ISO
40 9660 CD-ROM file system support" below, because that's the file
41 system used on CD-ROMs.
44 tristate "Parallel port ATAPI disks"
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
58 tristate "Parallel port ATAPI tapes"
61 This option enables the high-level driver for ATAPI tape devices
62 connected through a parallel port. If you chose to build PARIDE
63 support into your kernel, you may answer Y here to build in the
64 parallel port ATAPI disk driver, otherwise you should answer M
65 to build it as a loadable module. The module will be called pt.
66 You must also have at least one parallel port protocol driver in
67 your system. Among the devices supported by this driver is the
68 parallel port version of the HP 5GB drive.
71 tristate "Parallel port generic ATAPI devices"
74 This option enables a special high-level driver for generic ATAPI
75 devices connected through a parallel port. The driver allows user
76 programs, such as cdrtools, to send ATAPI commands directly to a
79 If you chose to build PARIDE support into your kernel, you may
80 answer Y here to build in the parallel port generic ATAPI driver,
81 otherwise you should answer M to build it as a loadable module. The
82 module will be called pg.
84 You must also have at least one parallel port protocol driver in
87 This driver implements an API loosely related to the generic SCSI
88 driver. See <file:include/linux/pg.h>. for details.
90 You can obtain the most recent version of cdrtools from
91 <ftp://ftp.berlios.de/pub/cdrecord/>. Versions 1.6.1a3 and
92 later fully support this driver.
94 comment "Parallel IDE protocol modules"
98 tristate "ATEN EH-100 protocol"
101 This option enables support for the ATEN EH-100 parallel port IDE
102 protocol. This protocol is used in some inexpensive low performance
103 parallel port kits made in Hong Kong. If you chose to build PARIDE
104 support into your kernel, you may answer Y here to build in the
105 protocol driver, otherwise you should answer M to build it as a
106 loadable module. The module will be called aten. You must also
107 have a high-level driver for the type of device that you want to
111 tristate "MicroSolutions backpack (Series 5) protocol"
114 This option enables support for the Micro Solutions BACKPACK
115 parallel port Series 5 IDE protocol. (Most BACKPACK drives made
116 before 1999 were Series 5) Series 5 drives will NOT always have the
117 Series noted on the bottom of the drive. Series 6 drivers will.
119 In other words, if your BACKPACK drive doesn't say "Series 6" on the
120 bottom, enable this option.
122 If you chose to build PARIDE support into your kernel, you may
123 answer Y here to build in the protocol driver, otherwise you should
124 answer M to build it as a loadable module. The module will be
125 called bpck. You must also have a high-level driver for the type
126 of device that you want to support.
129 tristate "MicroSolutions backpack (Series 6) protocol"
130 depends on PARIDE && !64BIT
132 This option enables support for the Micro Solutions BACKPACK
133 parallel port Series 6 IDE protocol. (Most BACKPACK drives made
134 after 1999 were Series 6) Series 6 drives will have the Series noted
135 on the bottom of the drive. Series 5 drivers don't always have it
138 In other words, if your BACKPACK drive says "Series 6" on the
139 bottom, enable this option.
141 If you chose to build PARIDE support into your kernel, you may
142 answer Y here to build in the protocol driver, otherwise you should
143 answer M to build it as a loadable module. The module will be
144 called bpck6. You must also have a high-level driver for the type
145 of device that you want to support.
148 tristate "DataStor Commuter protocol"
151 This option enables support for the Commuter parallel port IDE
152 protocol from DataStor. If you chose to build PARIDE support
153 into your kernel, you may answer Y here to build in the protocol
154 driver, otherwise you should answer M to build it as a loadable
155 module. The module will be called comm. You must also have
156 a high-level driver for the type of device that you want to support.
159 tristate "DataStor EP-2000 protocol"
162 This option enables support for the EP-2000 parallel port IDE
163 protocol from DataStor. If you chose to build PARIDE support
164 into your kernel, you may answer Y here to build in the protocol
165 driver, otherwise you should answer M to build it as a loadable
166 module. The module will be called dstr. You must also have
167 a high-level driver for the type of device that you want to support.
170 tristate "FIT TD-2000 protocol"
173 This option enables support for the TD-2000 parallel port IDE
174 protocol from Fidelity International Technology. This is a simple
175 (low speed) adapter that is used in some portable hard drives. If
176 you chose to build PARIDE support into your kernel, you may answer Y
177 here to build in the protocol driver, otherwise you should answer M
178 to build it as a loadable module. The module will be called ktti.
179 You must also have a high-level driver for the type of device that
183 tristate "FIT TD-3000 protocol"
186 This option enables support for the TD-3000 parallel port IDE
187 protocol from Fidelity International Technology. This protocol is
188 used in newer models of their portable disk, CD-ROM and PD/CD
189 devices. If you chose to build PARIDE support into your kernel, you
190 may answer Y here to build in the protocol driver, otherwise you
191 should answer M to build it as a loadable module. The module will be
192 called fit3. You must also have a high-level driver for the type
193 of device that you want to support.
196 tristate "Shuttle EPAT/EPEZ protocol"
199 This option enables support for the EPAT parallel port IDE protocol.
200 EPAT is a parallel port IDE adapter manufactured by Shuttle
201 Technology and widely used in devices from major vendors such as
202 Hewlett-Packard, SyQuest, Imation and Avatar. If you chose to build
203 PARIDE support into your kernel, you may answer Y here to build in
204 the protocol driver, otherwise you should answer M to build it as a
205 loadable module. The module will be called epat. You must also
206 have a high-level driver for the type of device that you want to
210 bool "Support c7/c8 chips"
211 depends on PARIDE_EPAT
213 This option enables support for the newer Shuttle EP1284 (aka c7 and
214 c8) chip. You need this if you are using any recent Imation SuperDisk
218 tristate "Shuttle EPIA protocol"
221 This option enables support for the (obsolete) EPIA parallel port
222 IDE protocol from Shuttle Technology. This adapter can still be
223 found in some no-name kits. If you chose to build PARIDE support
224 into your kernel, you may answer Y here to build in the protocol
225 driver, otherwise you should answer M to build it as a loadable
226 module. The module will be called epia. You must also have a
227 high-level driver for the type of device that you want to support.
230 tristate "Freecom IQ ASIC-2 protocol"
233 This option enables support for version 2 of the Freecom IQ parallel
234 port IDE adapter. This adapter is used by the Maxell Superdisk
235 drive. If you chose to build PARIDE support into your kernel, you
236 may answer Y here to build in the protocol driver, otherwise you
237 should answer M to build it as a loadable module. The module will be
238 called friq. You must also have a high-level driver for the type
239 of device that you want to support.
242 tristate "FreeCom power protocol"
245 This option enables support for the Freecom power parallel port IDE
246 protocol. If you chose to build PARIDE support into your kernel, you
247 may answer Y here to build in the protocol driver, otherwise you
248 should answer M to build it as a loadable module. The module will be
249 called frpw. You must also have a high-level driver for the type
250 of device that you want to support.
253 tristate "KingByte KBIC-951A/971A protocols"
256 This option enables support for the KBIC-951A and KBIC-971A parallel
257 port IDE protocols from KingByte Information Corp. KingByte's
258 adapters appear in many no-name portable disk and CD-ROM products,
259 especially in Europe. If you chose to build PARIDE support into your
260 kernel, you may answer Y here to build in the protocol driver,
261 otherwise you should answer M to build it as a loadable module. The
262 module will be called kbic. You must also have a high-level driver
263 for the type of device that you want to support.
266 tristate "KT PHd protocol"
269 This option enables support for the "PHd" parallel port IDE protocol
270 from KT Technology. This is a simple (low speed) adapter that is
271 used in some 2.5" portable hard drives. If you chose to build PARIDE
272 support into your kernel, you may answer Y here to build in the
273 protocol driver, otherwise you should answer M to build it as a
274 loadable module. The module will be called ktti. You must also
275 have a high-level driver for the type of device that you want to
279 tristate "OnSpec 90c20 protocol"
282 This option enables support for the (obsolete) 90c20 parallel port
283 IDE protocol from OnSpec (often marketed under the ValuStore brand
284 name). If you chose to build PARIDE support into your kernel, you
285 may answer Y here to build in the protocol driver, otherwise you
286 should answer M to build it as a loadable module. The module will
287 be called on20. You must also have a high-level driver for the
288 type of device that you want to support.
291 tristate "OnSpec 90c26 protocol"
294 This option enables support for the 90c26 parallel port IDE protocol
295 from OnSpec Electronics (often marketed under the ValuStore brand
296 name). If you chose to build PARIDE support into your kernel, you
297 may answer Y here to build in the protocol driver, otherwise you
298 should answer M to build it as a loadable module. The module will be
299 called on26. You must also have a high-level driver for the type
300 of device that you want to support.