Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:12171 comp.os.386bsd.misc:3083 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!uwm.edu!math.ohio-state.edu!howland.reston.ans.net!europa.eng.gtefsd.com!MathWorks.Com!news2.near.net!bloom-beacon.mit.edu!ai-lab!life.ai.mit.edu!mycroft From: mycroft@duality.gnu.ai.mit.edu (Charles M. Hannum) Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.misc Subject: Re: BT445C == No FreeBSD??? Date: 08 Aug 1994 07:23:39 GMT Organization: MIT Artificial Intelligence Lab Lines: 25 Message-ID: <MYCROFT.94Aug8032339@duality.gnu.ai.mit.edu> References: <31vk03$mdk@tekgen.bv.tek.com> <31vs36$qgv@tekgen.bv.tek.com> <Cu4w68.99B@tfs.com> <DERAADT.94Aug6165915@newt.fsa.ca> <Cu6KIp.6B8@tfs.com> NNTP-Posting-Host: duality.ai.mit.edu In-reply-to: julian@tfs.com's message of Sun, 7 Aug 1994 19:52:01 GMT In article <Cu6KIp.6B8@tfs.com> julian@tfs.com (Julian Elischer) writes: 386bsd used to do this with the SCSI drivers, but it got broken in patchlevel 2.4 and in FreeBSD1.x Actually, that's not quite right. While the original 386BSD code worked better with respect to dynamically allocating IRQs, it was never able to share them. The interrupt handling I wrote for NetBSD does. (FYI, the interface I chose is very similar to BSDI, though I've only seen the BSDI document describing it, and not their source code. The one difference I can think of was made to support unloading of drivers, which may require removing an interrupt handler.) The flexibility of this interrupt handler registration/deregistration system also makes PCI interrupt support very easy. -- - Charles Hannum NetBSD group Working ports: i386, hp300, amiga, sun4c, mac68k, pc532, da30. In progress: sun3, pmax, vax, sun4m, alpha, sun4.