From owner-freebsd-hackers Thu Apr 17 16:01:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA12933 for hackers-outgoing; Thu, 17 Apr 1997 16:01:18 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA12918 for ; Thu, 17 Apr 1997 16:01:13 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.7.3) id JAA13513; Fri, 18 Apr 1997 09:00:54 +1000 (EST) Date: Fri, 18 Apr 1997 09:00:53 +1000 (EST) From: "Daniel O'Callaghan" To: dennis cc: hackers@FreeBSD.ORG Subject: Re: Probing deflugalty In-Reply-To: <3.0.32.19970417185259.00b2cdf0@etinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 17 Apr 1997, dennis wrote: > At 08:48 AM 4/18/97 +1000, Daniel O'Callaghan wrote: > > > >Dennis, I have a machine with ed0 (ISA), ed3 (PCI), ed4 (PCI) > > > >Putting the 'device dev0' in makes sure the code is included, but > >numbering starts after the ISA numbers. > > > > Uh....PCIs are probed first, so how would the above work...it makes > much more sense for the PCI boards to be first (ie ed0, ed1) and > the isa cards last, since you can specify the isa cards device name, > but the PCI device name is dependent on whats in the system. Like I said, numbering starts *after* the ISA numbers. I tried a kernel config with ed0 ed1 ed2 at isa .... What happened was the PCI cards started at ed3 and ed4. So just added ed0 at isa ed1 at isa ed2 at isa ed3 and now I have the flexibility of putting in more ISA cards if necessary, and the PCI cards start at 3. ISA cards won't automatically number themselves, so it makes sense to start the number for PCI *after* all of the defined ISA devices. I have not looked at the code, but I assume that the PCI attach code finds the end of the ISA devices somehow. Cheers, Danny