Matthew Jacob sez:
# 
# >From owner-port-sparc@NetBSD.ORG Mon Oct 14 20:05:36 1996
# [ WAD O' STUFF DELETED ] 
# ># I moved the drive from ID 4 to ID 3 (which moved it to an ID with
# ># disconnect disabled) and the problem went away.
# >
# >Read your latest GENERIC config file and you can tweak your disconnect and
# >reselect bits.  It's awfully nice that a) they exist and b) they are separat
# e
# >bits!
# >
# 
# Why are these even needing to be settable things at all??????????????

Because there are devices out there which cannot handle
reselect/disconnect and/or sync negotiation, and because there are devices
out there which will really bog your system down or take errors if you
attempt to use them without disconnect/reselect (tape drives come to
mind).  And because it's a non-trivial fix to make the driver
automagically shut off disconnect/reselect/sync negotiation if it fails.

[Non-trivial to me, anyway -- I tried and couldn't get the settings to
 stick, even though the printf to be printed once the flag bit got
 set got printed and I ended up with a whole bunch of "(you should not
 see this message)" messages on my console.  So I must have been doing
 something wrong, because while the flag bit was set, the driver wasn't
 recognizing it later on down the line.  I inserted code which, once the
 RESELECT error was hit, set the appropriate bit on the device.  But
 it seems that once the driver attaches, changing the mode bit doesn't
 seem to help.]

				--*greywolf;