Date: Wed, 04 Sep 2002 10:18:12 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Bruce Evans <bde@zeta.org.au> Cc: current@freebsd.org Subject: Re: PUC_FASTINTR broken Message-ID: <98247.1031127492@critter.freebsd.dk> In-Reply-To: Your message of "Wed, 04 Sep 2002 18:02:48 %2B1000." <20020904175411.B638-100000@gamplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20020904175411.B638-100000@gamplex.bde.org>, Bruce Evans writes: >% RCS file: /home/ncvs/src/sys/dev/puc/puc.c,v >% Working file: puc.c >% head: 1.14 >% ... >% ---------------------------- >% revision 1.14 >% date: 2002/09/03 11:22:13; author: phk; state: Exp; lines: +3 -10 >% Fix interrupt registration: >% >% PUC devices live on pccard or pci so INTR_FAST is never really an option. >% Don't try to register the interrupt as fast and don't allow the children >% to do so either. >% ---------------------------- > >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. >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. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?98247.1031127492>