From owner-freebsd-hackers  Thu Apr 17 16:15:43 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id QAA13784
          for hackers-outgoing; Thu, 17 Apr 1997 16:15:43 -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 QAA13776
          for <hackers@FreeBSD.ORG>; Thu, 17 Apr 1997 16:15:37 -0700 (PDT)
Received: from ntws (ntws.etinc.com [204.141.95.142]) by etinc.com (8.8.3/8.6.9) with SMTP id TAA29706; Thu, 17 Apr 1997 19:22:56 -0400 (EDT)
Message-Id: <3.0.32.19970417191432.00b5d890@etinc.com>
X-Sender: dennis@etinc.com
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Thu, 17 Apr 1997 19:14:34 -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 09:00 AM 4/18/97 +1000, Daniel O'Callaghan wrote:
>
>
>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
>
What version are you running? I dont think 2.2.1 works that way.....

Dennis