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