From owner-freebsd-hackers  Fri Apr 18 09:50:55 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA17064
          for hackers-outgoing; Fri, 18 Apr 1997 09:50:55 -0700 (PDT)
Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA17045
          for <hackers@freebsd.org>; Fri, 18 Apr 1997 09:50:45 -0700 (PDT)
Received: from x14.mi.uni-koeln.de (annexr3-2.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA09523
  (5.67b/IDA-1.5 for <hackers@freebsd.org>); Fri, 18 Apr 1997 18:50:29 +0200
Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id SAA08985; Fri, 18 Apr 1997 18:50:28 +0200 (CEST)
Message-Id: <19970418185027.62509@x14.mi.uni-koeln.de>
Date: Fri, 18 Apr 1997 18:50:27 +0200
From: Stefan Esser <se@freebsd.org>
To: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
Cc: dennis <dennis@etinc.com>, hackers@freebsd.org
Subject: Re: Probing deflugalty
References: <3.0.32.19970417185259.00b2cdf0@etinc.com> <Pine.BSF.3.91.970418085541.10264R-100000@panda.hilink.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.68
In-Reply-To: <Pine.BSF.3.91.970418085541.10264R-100000@panda.hilink.com.au>; from Daniel O'Callaghan on Fri, Apr 18, 1997 at 09:00:53AM +1000
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Apr 18, Daniel O'Callaghan <danny@panda.hilink.com.au> wrote:
> 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.

Yes, it does. The unit number in the PCI attach code
is initialized to "NED +1" ...

I had considered several possibilities when I wrote 
the ED and LNC PCI attach wrappers, and found this
to be the cleanest solution. If I get around to make
"config" more PCI-aware, I intend to make

device ed0 at pci?

not reserve unit 0 for use by ISA ...

Regards, STefan