Re: [hatari-devel] Wrong MODE SENSE data length for page code 0x3f

[ Thread Index | Date Index | More lists.tuxfamily.org/hatari-devel Archives ]


> While debugging SCSI it might help to have a look at my implementation (still SCSI-I, but differences should not be too large):
> 
> https://sourceforge.net/p/previous/code/HEAD/tree/trunk/src/scsi.c
> 
> This has been thoroughly tested and works with all versions of NeXTstep and also with modern NetBSD. There is no Linux for NeXT, so I can’t test that one. From my experiences: Bus phases are especially tricky!

:) In this case let me add that it also might help to have a look at the
emulation code of https://github.com/uweseimet/scsi2pi. It has been tested
with NeXTstep, with the platforms listed on
https://github.com/PiSCSI/piscsi/wiki/Compatibility, and some others not
listed, also with BSD flavors.

But I guess that these sources of information are too complicated for
somebody who is not that much involved with SCSI, e.g. Eero. (At least this
is what I assume.)
Ensuring that Hatari does not return more than the number of bytes
requested, except for the special SCSI-1 case you pointed out, should be
ensured before trying to analyze any other issues.

Regarding bus phases, the fact that Linux requests a bus reset indicates
that something may be wrong here. On the other hand, if something was
fundamentally wrong, Hatari would not work with HDDRIVER, and probably also
not with CBHD.

By the way, I just tried my old Debian Linux (kernel 2.0.36) with Hatari:
A SCSI drive is detected correctly, but on the first READ(6) command there is
a timeout. Very strange. With real SCSI drives and SCSI2Pi exactly the same
Linux environment works fine when booting from a SCSI drive.

Best regards

Uwe



Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/