From owner-freebsd-current Wed Sep 4 2:36:28 2002 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 AE01337B400 for ; Wed, 4 Sep 2002 02:36:25 -0700 (PDT) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91DF043E6E for ; Wed, 4 Sep 2002 02:36:24 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id JAA12895; Wed, 4 Sep 2002 09:36:18 GMT Date: Wed, 4 Sep 2002 19:43:40 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Poul-Henning Kamp Cc: current@freebsd.org Subject: Re: PUC_FASTINTR broken In-Reply-To: <98247.1031127492@critter.freebsd.dk> Message-ID: <20020904193553.C880-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 4 Sep 2002, Poul-Henning Kamp wrote: > In message <20020904175411.B638-100000@gamplex.bde.org>, Bruce Evans writes: > >INTR_FAST is an option for pci devices. It was configured (not quite right) > >by the PUC_FASTINTR option, which should work just as well as the similar > >but much older CY_PCI_FASTINTR option (perfectly if the interrupt is not > >shared). > > It doesn't work right if the puc manages to register the interrupt as > FAST before we realize that it is shared. That is not a problem, since it is the configurer's responsibility to not use PUC_FASTINTR if it would not work. PUC_FASTINTR exists precisely to let the configurer make the correct choice, sint the driver and new-bus cannot. > >This change blows away the support for that option without even removing > >the option from conf/options, conf/NOTES or puc.4, and without even > >noting approval of the author of the code. > > I have yet to clean that fluff. Please don't. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message