Subject: Re: 2.0 can't nail down devices??
To: der Mouse <mouse@Rodents.Montreal.QC.CA>
From: Eduardo Horvath <eeh@NetBSD.org>
List: tech-kern
Date: 02/10/2005 16:41:34
On Thu, Feb 10, 2005 at 12:00:01AM -0500, der Mouse wrote:
> >> So I built a kernel with [...nail-down attempt...]
> >> Yet when I boot that kernel [...], I still get the default device
> >> probe order
> > Just a WAG, but do you have other "esp0"s declared in your kernel
> > config file?
> 
> Yes.  Here's grep output for "esp0":
> 
> esp0 at sbus0 slot 1 offset 0x8800000
> scsibus0 at esp0
> esp0    at obio0 addr 0xfa000000 level 4 flags 0x0000   # sun4/300
> esp0    at sbus0 slot ? offset ? flags 0x0000           # sun4c
> esp0    at dma0 flags 0x0000                            # sun4m
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

> fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
> iommu0 at mainbus0 addr 0x10000000: version 0x1/0x4, page-size 4096, range 64MB
> sbus0 at iommu0: clock = 25 MHz
> dma0 at sbus0 slot 4 offset 0x8400000: DMA rev 2
> esp0 at dma0 slot 4 offset 0x8800000 level 4: ESP200, 40MHz, SCSI ID 7
^^^^^^^^^^^^^^
> scsibus0 at esp0: 8 targets, 8 luns per target

I think what happens is that the on-board esp is first in the
OBP device tree, so it's being found and attached before your
fas is getting attached.  I expect those lines were added 
precisely to nail down the on-board devices as device 0 since
they are a bit redundant.  If you remove that line it should 
fix your attach order issue.  

Eduardo