Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:12156 comp.os.386bsd.misc:3081
Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.misc
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!tfs.com!julian
From: julian@tfs.com (Julian Elischer)
Subject: Re: BT445C == No FreeBSD???
Message-ID: <Cu6KIp.6B8@tfs.com>
Organization: TRW Financial Systems, Oakland, CA
References: <31vk03$mdk@tekgen.bv.tek.com> <31vs36$qgv@tekgen.bv.tek.com> <Cu4w68.99B@tfs.com> <DERAADT.94Aug6165915@newt.fsa.ca>
Date: Sun, 7 Aug 1994 19:52:01 GMT
Lines: 34
In article <DERAADT.94Aug6165915@newt.fsa.ca>,
Theo de Raadt <deraadt@fsa.ca> wrote:
>In article <Cu4w68.99B@tfs.com> julian@tfs.com (Julian Elischer) writes:
> the kernel is configured to use a different interrupt to that the board
> is configured for....
>
> check the interupt for the standard kernel, (I don't have one here) and
> set the board to match....
>
>I've decided to describe how the new NetBSD deals with this issue. I
>think it rather neat, and also worthwhile for people to know about.
>
[description of good system deleted....]
386bsd used to do this with the SCSI drivers, but it got broken in patchlevel
2.4 and in FreeBSD1.x
(the drivers would reconfigure themselves to match the hardware)
Bruce Evans rewrote the interrupt code, but unfortunatly, while it gave
greatly improved performance, it hard-coded some information about what
device was in what interupt vector at compile time..
This is being worked on and the NetBSD example will definitly looked at as
an example of correct functionality.
but until then, unfortunaltly the kernel config and the hardware need
to agree for freeBSD.
julian
+----------------------------------+ ______ _ __
| __--_|\ Julian Elischer | \ U \/ / On assignment
| / \ julian@tfs.com +------>x USA \ in a very strange
| ( OZ ) 300 lakeside Dr. oakland CA. \___ ___ | country !
+- X_.---._/ USA+(510) 645-3137(wk) \_/ \\
v