From owner-freebsd-hackers  Thu Apr 17 15:54:17 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA12354
          for hackers-outgoing; Thu, 17 Apr 1997 15:54:17 -0700 (PDT)
Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA12349
          for <hackers@FreeBSD.ORG>; Thu, 17 Apr 1997 15:54:09 -0700 (PDT)
Received: from ntws (ntws.etinc.com [204.141.95.142]) by etinc.com (8.8.3/8.6.9) with SMTP id TAA29546; Thu, 17 Apr 1997 19:01:23 -0400 (EDT)
Message-Id: <3.0.32.19970417185259.00b2cdf0@etinc.com>
X-Sender: dennis@etinc.com
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Thu, 17 Apr 1997 18:53:01 -0400
To: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
From: dennis <dennis@etinc.com>
Subject: Re: Probing deflugalty
Cc: hackers@FreeBSD.ORG
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

At 08:48 AM 4/18/97 +1000, Daniel O'Callaghan wrote:
>
>
>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
>

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.

Dennis