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