Date: Tue, 12 Dec 2000 00:26:01 -0800 From: Mike Smith <msmith@freebsd.org> To: mjacob@feral.com Cc: alpha@FreeBSD.ORG Subject: Re: -current not bootable on Rawhide (as4100) Message-ID: <200012120826.eBC8Q1302477@mass.osd.bsdi.com> In-Reply-To: Your message of "Mon, 11 Dec 2000 23:56:23 PST." <Pine.BSF.4.21.0012112354190.1498-100000@beppo.feral.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Does the kernel config have EISA in it? It just occurs to me that if you
> > don't, you won't get the ISA bus (because the bridge is PCI:EISA).
>
> D'oh!
>
> This is what I get for just doing this stuff with half a brain, which, as you
> know, makes things pretty small for now. I just porked my system, so I can't
> fix this until I get in tomorrow.
You mean this is what I get. 8) At any rate, there are a couple of
solutions. One is to say "if you have a PCI:EISA bridge, you must have
EISA support to get ISA". I don't really like that.
Another is to match an EISA bridge as an ISA bridge, but that's also bad.
A third, and I kinda like this one, is to build the EISA bridge support
anytime you build PCI. The EISA bridge code will hang out a hook for an
EISA bus (which doesn't have to be there), but it will also hang out a
hook for an ISA bus, which might be. This is the way it used to "work"
as well...
--
... 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-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200012120826.eBC8Q1302477>