Yeah, Chris sent me private mail about this. I asked him whether this was
publicly available for usage in *BSD but haven't heard back.


On Wed, 16 Aug 2000, Kurt J. Lidl wrote:

> On Wed, Aug 16, 2000 at 10:58:11AM -0700, Matthew Jacob wrote:
> > No. It's not. It's *close*, but I believe it's either a ESP-266 or
> > ESP366 chip, not the ESP-100A that esp(4) drives. I have documentation if
> > somebody wants to take this on (ENOTIME). 
> 
> It is an ESP 366 chip.  This is the same part that is on the motherboard
> of the Ultra2 workstation.
> 
> > > I have a SunSwift Fast Ethernet (hme)/Wide SCSI (fas) Sbus card, sun 
> > > part # 501-2739. Alas, NetBSD pops up this SCSI controller as "not 
> > > configured" at boot. Is this not another variant of the "esp" and 
> > > therefore a trivial thing to enable?
> 
> For the record, here is what BSD/OS probes the on-board scsi controller
> on a SS20 as (FAS100A), and also what it probes the SunSwift in the same
> machine.  Maybe this will help out:
> 
> espdma0 at sbus0 slot 15 offset 0x400000: rev 2
> esp0 at espdma0 slot 15 offset 0x800000 pri 4
> esp0: FAS100A (family code 0, version 2) @ 40 MHz, initiator id 7
> [...]
> hme0 at sbus0 slot 2 offsets 0x8c00000,0x8c02000,0x8c04000,0x8c06000,0x8c07000 pri 7: hardware address 08:00:20:71:bc:48
> nsphy0 at hme0 phy 1: 83840 r1 10baseT 10baseT-FDX 100baseTX 100baseTX-FDX Auto
> esp1 at sbus0 slot 2 offsets 0x8800000,0x8810000 pri 5
> esp1: FAS366 (family code 10, version 5) @ 40 MHz, initiator id 7
> 
> -Kurt
>