From owner-freebsd-current@FreeBSD.ORG Sun Jun 20 17:09:25 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0E44E16A4CE for ; Sun, 20 Jun 2004 17:09:25 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABA2C43D53 for ; Sun, 20 Jun 2004 17:09:24 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.11/8.12.11) with ESMTP id i5KH8DjV005690; Sun, 20 Jun 2004 11:08:14 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 20 Jun 2004 11:08:16 -0600 (MDT) Message-Id: <20040620.110816.26780069.imp@bsdimp.com> To: rik@cronyx.ru From: "M. Warner Losh" In-Reply-To: <40D2E22A.40702@cronyx.ru> References: <40D1D2A8.2070000@cronyx.ru> <20040618093024.X1609@gamplex.bde.org> <40D2E22A.40702@cronyx.ru> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: How to catch interrupt X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Jun 2004 17:09:25 -0000 In message: <40D2E22A.40702@cronyx.ru> Roman Kurakin 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). Warner