NetBSD master CVS tree commits

[source%NetBSD.ORG@localhost]

mikel
Wed Mar 26 23:30:26 PST 1997
Update of /cvsroot/src/sys/ufs/ufs
In directory netbsd1:/var/slash-tmp/cvs-serv1173/src/sys/ufs/ufs

Modified Files:
        ufs_vnops.c 
Log Message:
POSIX.1 specifies that a failed link() to a directory must return EPERM,
  and EMLINK was not documented; from Klaus Klein in PR standards/3397.
Also documented EOPNOTSUPP for filesystems that don't support hard links.


mikel
Wed Mar 26 23:30:27 PST 1997
Update of /cvsroot/src/lib/libc/sys
In directory netbsd1:/var/slash-tmp/cvs-serv1173/src/lib/libc/sys

Modified Files:
        link.2 
Log Message:
POSIX.1 specifies that a failed link() to a directory must return EPERM,
  and EMLINK was not documented; from Klaus Klein in PR standards/3397.
Also documented EOPNOTSUPP for filesystems that don't support hard links.


scottr
Wed Mar 26 23:30:41 PST 1997
Update of /cvsroot/src/sys/dev/ic
In directory netbsd1:/var/slash-tmp/cvs-serv1105

Modified Files:
        ncr5380sbc.c 
Log Message:
Work around an ambiguity in the SCSI spec.  Some implementations,
particularly older ones, don't do a SAVE DATA POINTER before disconnecting.
When the driver reconnects, it does an implicit RESTORE POINTERS, and
restores the data pointer from *before* the last transfer.  If the driver
calculates the residual using the data pointer and doesn't account for
this, the residual will be wrong.

What we do is test for the SDEV_AUTOSAVE quirk when we see a disconnect
message, falling through to do a SAVE DATA POINTER if the quirk applies
to this target.

The workaround was suggested by Mycroft, who also provided the explanation
of the problem.  Actual code was (mostly) ripped off from the 53C9x driver.


scottr
Wed Mar 26 23:37:55 PST 1997
Update of /cvsroot/src/sys/scsi
In directory netbsd1:/var/slash-tmp/cvs-serv1554

Modified Files:
        scsiconf.c 
Log Message:
Add SDEV_AUTOSAVE quirks for IBM 0663H{08,12} disks