At 11:26 AM 4/23/2002, Manuel Bouyer wrote:
>Hi,
>those following source-changes will have noticed I've done some haking on the
>siop driver these days.
>I've added a new driver, esiop, which match the siop chips with the
>requested properties (basically enouth general purpose registers, the
>load/store instruction and "aithmetic ops on 2 registers).

With -current as of a few minutes ago, both siop and esiop fail to
negotiate properly with my SCSI drive:

Before:
NetBSD 1.5ZC (PILOT) #54: Wed Apr  3 23:55:17 PST 2002
[...]
siop0 at pci1 dev 5 function 0: Symbios Logic 53c896 (ultra2-wide scsi)
siop0: using on-board RAM
siop0: interrupting at irq 9
[...]
sd0 at scsibus1 target 1 lun 0: <IBM, DXHS36D, 0162> SCSI3 0/direct fixed
sd0: 34732 MB, 11494 cyl, 20 head, 309 sec, 512 bytes/sect x 71132960 sectors
sd0: sync (25.0ns offset 15), 16-bit (80.000MB/s) transfers, tagged queueing

Now:

sd0 at scsibus1 target 1 lun 0: <IBM, DXHS36D, 0162> SCSI3 0/direct fixed
sd0: 34732 MB, 11494 cyl, 20 head, 309 sec, 512 bytes/sect x 71132960 sectors
sd0: async, 8-bit transfers, tagged queueing

Until this is fixed I can't run bleeding edge current. :(  Just thought
you'd like to know.

-- 
Matt Thomas               Internet:   matt@3am-software.com
3am Software Foundry      WWW URL:    http://www.3am-software.com/bio/matt/
Cupertino, CA             Disclaimer: I avow all knowledge of this message