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