The following reply was made to PR port-mac68k/9679; it has been noted by GNATS.

From: Hauke Fath <hauke@Espresso.Rhein-Neckar.DE>
To: gnats-bugs@netbsd.org
Cc: port-mac68k-maintainer@netbsd.org, gnats-admin@netbsd.org,
	hauke@Espresso.Rhein-Neckar.DE, Chuck Silvers <chuq@chuq.com>,
	Dave Huang <khym@azeotrope.org>
Subject: Re: port-mac68k/9679 -- Using scsi/libscsi lets mac68k sbc driver
  dump core
Date: Mon, 16 Jan 2006 00:16:57 +0100

 At 17:05 Uhr +0000 15.1.2006, Hauke Fath wrote:
 > From looking at mac68k/dev/mac68k5380.c, am I wrong in assuming that the
 > ncrscsi driver would suffer from the same problem? (Test kernel is still a
 > few hours from completion.)
 
 Surprise -- the ncrscsi driver seems to handle this properly:
 
 mirth# ./scsi -f /dev/rsd0c -m8 -P3 -v
 IC:  0
 ABPF:  0
 CAP:  0
 DISC:  0
 SIZE:  0
 WCE:  0
 MF:  0
 RCD:  1
 Demand Retention Priority:  0
 Write Retention Priority:  0
 Disable Pre-fetch Transfer Length:  0
 Minimum Pre-fetch:  0
 Maximum Pre-fetch:  32
 Maximum Pre-fetch Ceiling:  63
 mirth# dmesg | grep scsi
 ncrscsi0 at obio0
 scsibus0 at ncrscsi0 channel 0: 8 targets, 8 luns per target
 scsibus0: waiting 2 seconds for devices to settle...
 sd0 at scsibus0 target 0 lun 0: <CONNER, CP30540 545MB3.5, B0BC> disk fixed
 sd1 at scsibus0 target 2 lun 0: <QUANTUM, FIREBALL_TM1280S, 300X> disk fixed
 mirth#
 
 	hauke
 
 --
 "It's never straight up and down"     (DEVO)