• Home
  • Raw
  • Download

Lines Matching refs:build

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
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
33 build it as a loadable module. The module will be called pcd. You
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
49 to build it as a loadable module. The module will be called pf.
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
63 to build it as a loadable module. The module will be called pt.
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
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
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
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
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
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
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.
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
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
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
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
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
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
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
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
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