From owner-freebsd-hackers  Thu Apr 17 15:48:38 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA11968
          for hackers-outgoing; Thu, 17 Apr 1997 15:48:38 -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 PAA11961
          for <hackers@FreeBSD.ORG>; Thu, 17 Apr 1997 15:48:28 -0700 (PDT)
Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.7.3) id IAA13451; Fri, 18 Apr 1997 08:48:10 +1000 (EST)
Date: Fri, 18 Apr 1997 08:48:09 +1000 (EST)
From: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
To: dennis <dennis@etinc.com>
cc: hackers@FreeBSD.ORG
Subject: Re: Probing deflugalty
In-Reply-To: <3.0.32.19970417142522.00a4bc50@etinc.com>
Message-ID: <Pine.BSF.3.91.970418084450.10264P-100000@panda.hilink.com.au>
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:

> 
> With the following configuration:
> 
> device dev0
> device dev0 at isa? port 0x300
> 
> If a PCI device is found, the ISA dev0 really shouldn't be probed, but
> it is.

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.

Danny