> > lp0: using parport0 (polling).
>
> This indicates the parallel port driver is using polled, as opposed to
> interrupt-driven, operation. IRQ auto-detection can go wrong with horrible
> results, so polled is the default. See above for how to change to
> interrupt-driven mode.
>
> Polling the parallel port controller for status updates does use some CPU
> time, but I believe it is fairly insignificant. YMMV.
One problem I've found (and this was /years/ ago, so it may have changed)
with polling is that it was slower-than-dirt. Didn't influence the
machine's performance perceptably, but apparently the polling rate was so
slow that your printer throughput wasn't anything to write home about.
This may have changed, as, again, this was many moons ago (and, for that
matter, using LPT3:, which is why I had to use polling in the first
place.)
-Ken
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
