Date: Mon, 21 Jun 2004 01:32:41 +0400 From: Roman Kurakin <rik@cronyx.ru> To: "M. Warner Losh" <imp@bsdimp.com> Cc: freebsd-current@freebsd.org Subject: Re: How to catch interrupt Message-ID: <40D60279.4060602@cronyx.ru> In-Reply-To: <20040620.110816.26780069.imp@bsdimp.com> References: <40D1D2A8.2070000@cronyx.ru> <20040618093024.X1609@gamplex.bde.org> <40D2E22A.40702@cronyx.ru> <20040620.110816.26780069.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
M. Warner Losh: >In message: <40D2E22A.40702@cronyx.ru> > Roman Kurakin <rik@cronyx.ru> 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 isa_irq_pending()? rik > >Warner >_______________________________________________ >freebsd-current@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40D60279.4060602>