On Wed, Oct 17, 2001 at 09:21:33PM +1000, matthew green wrote:

 >    | hme0 at pci1 dev 1 function 1: address 08:00:20:f9:8c:7a
 >    | ukphy0 at hme0 phy 0: Generic IEEE 802.3u media interface
 >    | ukphy0: OUI 0x0006b8, model 0x000c, rev. 1
 >    | ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 >    | ukphy1 at hme0 phy 1: Generic IEEE 802.3u media interface
 >    | ukphy1: OUI 0x0006b8, model 0x000c, rev. 1
 >    | ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 >    
 >    What does `ifconfig -a' print out?
 > 
 > 
 > also, what does the prom show ?  what does solaris `prtconf -pv'
 > show ?  thorpej, you seen this ever before?

I thought about it when I got up this morning (amazing the sorts of things
that pop into your head before you've had a cup of coffee :-), and suspect
I know what's going on here...

My guess is that the two HMEs share a single serial bus for PHY management
(PHY management and the PHY data interface are done on separate wires).
That is why you see both PHYs on the first HME instance.

The reason for not seeing the second HME is probably an artifact of
the PCI "devorder" stuff that the sparc64 port uses -- that's just a
guess anyway ... Solaris obviously sees the second HME at device 3,
but NetBSD isn't for whatever reason, and the PCI "devorder" stuff is
the only thing that pops immediately to mind.

Can you please go to each HME's node at the OFW prompt, and type
".properties", and send the output?  Also an "ls" from the node
above the HMEs.

-- 
        -- Jason R. Thorpe <thorpej@wasabisystems.com>