Lines Matching refs:driver
15 This option enables the high-level driver for IDE-type disk devices
18 parallel port IDE driver, otherwise you should answer M to build
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
29 This option enables the high-level driver for ATAPI CD-ROM devices
32 parallel port ATAPI CD-ROM driver, otherwise you should answer M to
34 must also have at least one parallel port protocol driver in your
35 system. Among the devices supported by this driver are the
45 This option enables the high-level driver for ATAPI disk devices
48 parallel port ATAPI disk driver, otherwise you should answer M
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
59 This option enables the high-level driver for ATAPI tape devices
62 parallel port ATAPI disk driver, otherwise you should answer M
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
72 This option enables a special high-level driver for generic ATAPI
73 devices connected through a parallel port. The driver allows user
78 answer Y here to build in the parallel port generic ATAPI driver,
82 You must also have at least one parallel port protocol driver in
85 This driver implements an API loosely related to the generic SCSI
86 driver. See <file:include/linux/pg.h>. for details.
90 later fully support this driver.
103 protocol driver, otherwise you should answer M to build it as a
105 have a high-level driver for the type of device that you want to
121 answer Y here to build in the protocol driver, otherwise you should
123 called bpck. You must also have a high-level driver for the type
140 answer Y here to build in the protocol driver, otherwise you should
142 called bpck6. You must also have a high-level driver for the type
152 driver, otherwise you should answer M to build it as a loadable
154 a high-level driver for the type of device that you want to support.
163 driver, otherwise you should answer M to build it as a loadable
165 a high-level driver for the type of device that you want to support.
175 here to build in the protocol driver, otherwise you should answer M
177 You must also have a high-level driver for the type of device that
188 may answer Y here to build in the protocol driver, otherwise you
190 called fit3. You must also have a high-level driver for the type
202 the protocol driver, otherwise you should answer M to build it as a
204 have a high-level driver for the type of device that you want to
223 driver, otherwise you should answer M to build it as a loadable
225 high-level driver for the type of device that you want to support.
234 may answer Y here to build in the protocol driver, otherwise you
236 called friq. You must also have a high-level driver for the type
245 may answer Y here to build in the protocol driver, otherwise you
247 called frpw. You must also have a high-level driver for the type
258 kernel, you may answer Y here to build in the protocol driver,
260 module will be called kbic. You must also have a high-level driver
271 protocol driver, otherwise you should answer M to build it as a
273 have a high-level driver for the type of device that you want to
283 may answer Y here to build in the protocol driver, otherwise you
285 be called on20. You must also have a high-level driver for the
295 may answer Y here to build in the protocol driver, otherwise you
297 called on26. You must also have a high-level driver for the type