Philip Blundell (pb@nexus.co.uk)
Wed, 01 Apr 1998 09:53:37 +0100
>So, my plan is to utilise tunelp. lp defaults to polling until given a
>non-zero IRQ by tunelp -i. Then it uses whatever IRQ parport found, or
We can make a new tunelp that doesn't take a parameter to -i. This would make
it less confusing.
>It would also be good to have a module parameter to enable
>interrupt-driven operation from the outset. A kernel parameter would be
>good too, but I can't think of a good syntax for it (anyone?).
I guess another option would be to use IRQs if the user specified them when
loading the module or booting the kernel, but default to polling if the IRQ
line had to be probed. I don't think I like that though.
p.
-- To unsubscribe, send mail to: linux-parport-request@torque.net --
-- with the single word "unsubscribe" in the body of the message. --
This archive was generated by hypermail 2.0b3 on Wed 30 Dec 1998 - 10:17:34 EST