Date: Thu, 02 Nov 2000 14:34:58 -0800 From: Mike Smith <msmith@freebsd.org> To: Jordan Hubbard <jkh@winston.osd.bsdi.com> Cc: stable@FreeBSD.org Subject: Re: i386/20379 Message-ID: <200011022234.eA2MYwF01536@mass.osd.bsdi.com> In-Reply-To: Your message of "Thu, 02 Nov 2000 14:17:58 PST." <26463.973203478@winston.osd.bsdi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > On the other hand, there *is* an easy workaround to turn them off, so in
> > the worst case we would have an escape route.
> >
> > Jordan, what's your feeling on this? I don't have a 450GX board to test
> > with. 8(
>
> I feel it looks like a small but smelly hack and I also have bad
> feelings about it. :) What's this "easy workaround to turn them off"
> you're alluding to?
set machdep.pci.bios="disable"
in the loader disables searching for (and thus use of) the PCI BIOS
interface. If you check back up the log for this PR, you'll see that an
earlier respondent has indicated that the PCI BIOS code on these boards
seems to DTRT where our own register-level code doesn't.
Alternatively (a POLA issue, I guess at worst) I can bring it in but
default it to "disable", so that people with this problem will have to
set it to "enable". Then it would become an errata issue.
As I mentioned elsewhere though, the PCI BIOS code has been remarkably
complaint-free over the last ~6mo or so in -current...
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view. [Dr. Fritz Todt]
V I C T O R Y N O T V E N G E A N C E
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200011022234.eA2MYwF01536>
