> On Tue, 22 Aug 2000, matthew green wrote:
> 
> | for SBUS, you mean.  the PCI `hme' chip also has the `ebus' on it... that's
> | why my hme card probes like:
> | 
> | Sun Microsystems PCIO Ebus2 (miscellaneous bridge, revision 0x01) at pci1 dev 3 function 0 not configured
> | hme1 at pci1 dev 3 function 1: address 08:00:20:a7:7d:25
> | ukphy0 at hme1 phy 1: Generic IEEE 802.3u media interface
> | ukphy0: OUI 0x00601d, model 0x000c, rev. 1
> | ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> | hme1: using vector 25 for interrupt
> 
> Yeah. the PCI card version (Freshchoice and Freshchoice-2 scsi/hme
> combo card) uses the Qlogic ISP-1040 chip. This is seen as a
> "isptwo" device, I believe, and uses the 'isp' driver in solaris.
> 
> I'm looking at one of these cards right now, and the chips on it are:
> 
> Qlogic ISP1040B

That's an isp(4) driver driven card for NetBSD, FreeBSD, OpenBSD. It probably
doesn't yet work with NetBSD/sparc64, but give it a try. I'll fix it RSN.

> Intel 21152-AB
> Sun STP2003QFP
> 
> both the scsi and hme parts have their own fcode. Sun doesnt have a
> 1040/HME ASIC like they do for the FAS366/HME (the FEPS STP2002 chip). It
> doesnt seem like Sun has any docs on the STP2003 anywhere on their site.