How to catch interrupt

Roman Kurakin rik at
Sun Jun 20 21:44:15 GMT 2004

M. Warner Losh:

>In message: <40D2E22A.40702 at>
>            Roman Kurakin <rik at> writes:
>: Ok. Thanks for information. I guess I need to remove this code from my 
>: driver.
>: This code is part of cx(4) and ctau(4) drivers. These cards are legacy 
>: ISA cards,
>: IRQ line could be set any (from a definite set). The only reason why we 
>: probe
>: for IRQ is to write to the user messages that IRQ is not functional - 
>: most probable
>: it is assigned fot PCI/PNP. After we add this code calls to our tech 
>: support with
>: question why device is not working (due to this reason) decreased twice.
>You can also use the watchdog timeout to good effect.  When the
>operation is done, you reset the watchdog.  When the timeout happens,
>you know that you don't have a working interrupt...  It won't happen
>at probe time, but will happen at a useful time (the first time the
>user tries to use it).
I already use this solution. And it wouldn't help in case of 
autodetection, since
adapter could use almost any IRQ and in this case driver should be smart to
take the right one from available.

Since sio also need this probably we should have much smarter 


>freebsd-current at mailing list
>To unsubscribe, send any mail to "freebsd-current-unsubscribe at"

More information about the freebsd-current mailing list