Hi guys ...
I can't say that I'm off to a roaring start ....
I can't seem to get my interrupt handler "registered". When I check
/proc/interrupts, irq is not listed. When I trigger it, nothing happens.
When I load the parport module, it does detect irq 7. In the init section of
my driver, I pass my function pointer to parport_register_device, call
parport_enable_irq and finally write the correct value to the control
Is there a subtelty I'm missing ?
On Wed, 24 Jul 2002, Tim Waugh wrote:
> On Wed, Jul 24, 2002 at 09:56:28AM -0400, Philippe Tanguay wrote:
> > * I think the 2.2 driver uses the "old" style parport linux driver. Would
> > it be worthwhile to make it use the newer interface ? I found the parport
> > programming howto written by Tim Waugh, but it certainly doesn't match the
> > API used in the 2.2 driver (haven't found any info on that...)
> > * Regardless of which parport API I go with, how do I hookup
> > interrupts to be fired when the ACK pin is triggered (I know about
> > the interuppt enable bit in the port control register, I need info
> > on how to install an interrupt handler in parport framework) ?
> The irq_func parameter of parport_register_device.
-- To unsubscribe, send mail to: email@example.com --
-- with the single word "unsubscribe" in the body of the message. --
This archive was generated by hypermail 2b29 : Thu Jul 25 2002 - 09:49:42 EDT