Depends on the card/solaris version they're migrating from.

I've had qfe cards that probed as 4 hme's or 4 qfe's on Solaris depending 
which version of the card/firmware/driver was in use.

James

>
>On Tue, Feb 20, 2001 at 04:55:25PM -0500, Jason Wright wrote:
>> On Tue, Feb 20, 2001 at 01:43:15PM -0500, Rob Quinn wrote:
>>>  http://www.netbsd.org/Ports/sparc/hardware.html says the qfe card is
>>> supported, though "not well tested". I don't see mention of it in the
>>> INSTALL or GENERIC conf files. How do I enable mine?
>> It's just a matter of adding SUNW,qfe as another name for the sbus hme driver
>> to match.  Looks like it only matches this in NetBSD:
>> 	SUNW,hme
>
> Thanks. I inserted an extra strcmp to hmematch_sbus in dev/sbus/if_hme_sbus.c
>and that did it. No problems so far, but I've only been running it for a few
>minutes, and only at 10baseT. The fact that it now comes up as hme instead of
>qfe might surprise people migrating from Solaris.
>
>hme0 at sbus0 slot 1 offset 0x8c00000 level 4 (ipl 7): address 08:00:20:82:32:64
>ukphy0 at hme0 phy 1: Generic IEEE 802.3u media interface
>ukphy0: OUI 0x00601d, model 0x000c, rev. 1
>ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
>hme1 at sbus0 slot 1 offset 0x8c10000 level 4 (ipl 7): address 08:00:20:82:32:64
>ukphy1 at hme1 phy 1: Generic IEEE 802.3u media interface
>ukphy1: OUI 0x00601d, model 0x000c, rev. 1
>ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
>hme2 at sbus0 slot 1 offset 0x8c20000 level 4 (ipl 7): address 08:00:20:82:32:64
>ukphy2 at hme2 phy 1: Generic IEEE 802.3u media interface
>ukphy2: OUI 0x00601d, model 0x000c, rev. 1
>ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
>hme3 at sbus0 slot 1 offset 0x8c30000 level 4 (ipl 7): address 08:00:20:82:32:64
>ukphy3 at hme3 phy 1: Generic IEEE 802.3u media interface
>ukphy3: OUI 0x00601d, model 0x000c, rev. 1
>ukphy3: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
>
>
>
>