Date: Wed, 6 Mar 1996 10:19:46 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: gibbs@freefall.freebsd.org (Justin T. Gibbs) Cc: terry@lambert.org, imb@scgt.oz.au, stable@FreeBSD.org, current@FreeBSD.org Subject: Re: 2842 and the disappearing file-system :-( Message-ID: <199603061719.KAA11164@phaeton.artisoft.com> In-Reply-To: <199603052339.PAA07251@freefall.freebsd.org> from "Justin T. Gibbs" at Mar 5, 96 03:39:57 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> >> >> Actually this appears to be a bug in eisaconf as it affects all > >> >> eisa scsi controllers at the moment. I'm looking into it, but the > >> >> problem is not obvious and doesn't occur in -current. > >> > > >> >He has a VESA controller... brain farts are contagious! > >> > >> He has a VESA controller that uses an EISA probe and so is > >> also affected. > > > >Ah. That's broken. 8-(. This must be a VESA/EISA box for it to > >see the EISA signature and hit the EISA code? > > The eisaconf code always probes for eisa ids if it is configured > in your system. It hasn't caused any conflicts on any system that > I've seen, and since we have at least one device driver that would > have to copy the same probe code in order to work, I decied to make > eisaconf work this way. So if it checked for the signature word and didn't "eisaconf" without it, and the probe were duped (or multiply referenced, anyway), then his problem would go away? I think EISA probing ought to be limited to EISA bus machines. Call me strange. 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199603061719.KAA11164>