From owner-freebsd-hackers Thu Apr 17 17:19:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA18106 for hackers-outgoing; Thu, 17 Apr 1997 17:19:06 -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 RAA18090 for ; Thu, 17 Apr 1997 17:19:00 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.7.3) id KAA13865; Fri, 18 Apr 1997 10:18:44 +1000 (EST) Date: Fri, 18 Apr 1997 10:18:43 +1000 (EST) From: "Daniel O'Callaghan" To: dennis cc: hackers@FreeBSD.ORG Subject: Re: Probing deflugalty In-Reply-To: <3.0.32.19970417185458.00b2d590@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: > >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. > > > >I'd sure hate it if I was not allowed to use a mixture of PCI and ISA > >cards from the same driver type. > My point here was that if ed0 is already attached that additional ed0 > probes should not be done.... Which is why the PCI numbering must start after the ISA. Maybe declaring 'device ed0' in the config file is misleading. Perhaps it should be 'device ed' or 'device ed pci'. After all, declaring 'device ed0' will allow any number of PCI ed cards. Danny