From owner-freebsd-hackers  Thu Apr 17 15:56:30 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA12547
          for hackers-outgoing; Thu, 17 Apr 1997 15:56:30 -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 PAA12534
          for <hackers@FreeBSD.ORG>; Thu, 17 Apr 1997 15:56:22 -0700 (PDT)
Received: from ntws (ntws.etinc.com [204.141.95.142]) by etinc.com (8.8.3/8.6.9) with SMTP id TAA29566; Thu, 17 Apr 1997 19:03:21 -0400 (EDT)
Message-Id: <3.0.32.19970417185458.00b2d590@etinc.com>
X-Sender: dennis@etinc.com
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Thu, 17 Apr 1997 18:55:00 -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.
>

My point here was that if ed0 is already attached that additional ed0
probes should not be done....

Dennis