Lines Matching refs:drivers

56 high-level drivers for each of the different types of supported devices: 
66 The high-level drivers function according to the relevant standards.
67 The third component of PARIDE is a set of low-level protocol drivers
91 the PARIDE drivers into your kernel, or to build them as modules.
94 as well as at least one of the high-level drivers and at least one
106 and high-level drivers that you would use:
123 2.1  Configuring built-in drivers
125 We recommend that you get to know how the drivers work and how to
127 kernel with the drivers built-in.
135 The high-level drivers accept a number of command line parameters, all
136 of which are documented in the source files in linux/drivers/block/paride.
140 if you have more than one device, you will need to tell the drivers
179 It is much faster and simpler to get to understand the PARIDE drivers
182 Note 1:  using these drivers with the "kerneld" automatic module loading
207 Finally, you can load high-level drivers for each kind of device that
219 but check the source files in linux/drivers/block/paride for more 
241 Once the drivers have been loaded, you can access PARIDE devices in the
273 With the device files and drivers in place, you can access PARIDE devices
328 The most common problems that people report with the PARIDE drivers
345 to each of the high-level drivers.  Please see the notes above, or
347 linux/drivers/block/paride.
356 multiple device environments, the PARIDE drivers will not do it 
363 your paride drivers as modules, and arrange to do the printer reset
364 before loading the PARIDE drivers. 
368 While a lot of testing has gone into these drivers to make them work
371 DOS with the manufacturer's drivers ?  If that doesn't yield any useful
375 appropriate drivers (you can load several protocol modules if you want)
386 The verbose=1 parameter will cause the drivers to log a trace of their