From owner-freebsd-alpha Tue Dec 12 0:32:52 2000 From owner-freebsd-alpha@FreeBSD.ORG Tue Dec 12 00:32:50 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 37ED237B400; Tue, 12 Dec 2000 00:32:50 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id AAA15021; Tue, 12 Dec 2000 00:32:56 -0800 Date: Tue, 12 Dec 2000 00:32:49 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Mike Smith Cc: alpha@FreeBSD.ORG Subject: Re: -current not bootable on Rawhide (as4100) In-Reply-To: <200012120826.eBC8Q1302477@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 12 Dec 2000, Mike Smith wrote: > > > 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. That's the NetBSD solution. > Another is to match an EISA bridge as an ISA bridge, but that's also bad. True. > > 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... If this was the change to conf/files, I'll try it in the morning. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message