|Re: [hatari-devel] SCSI emulation|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] SCSI emulation
- From: Thomas Huth <th.huth@xxxxxxxxx>
- Date: Sat, 1 Sep 2018 12:39:01 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1535798343; bh=iH+sZDjPod4sFQjUoBq6IP294V/kCetFKj934x0IgdM=; h=Date:From:To:Subject:From; b=V2RFciTWkjzUCGF0kPJ9g9nYtd6r7NAPtChBfyU8IY4eeFg2foScSiFeX9SshVKA/ qP/G/i4rPgBEUmdOvDKevlrlp6C580Xa21TSFEXO2/4JOQMLPhrYDeEOZHjF9RriLr 2shgokj21s2WXEZwTq+boN1oDNWYol2LZDvNZKTHRsakQogiGzwuTR2jme0ZGEVwCh nDhIgHo//pKmN4ljFv7tX8kRmgomilbNRLXu1cu65h+fJzhOAvkgxya//T2d07ybav dfh8hKvdHP77BteeUDzrl5qDEfTXY5VY4JBOzAVli1M3jPoGyU99MjqHIq5JoZi4bk nZmz2Z2gDmxrg==
Am Sun, 26 Aug 2018 09:11:10 +0200
schrieb Uwe Seimet <Uwe.Seimet@xxxxxxxxx>:
> Hi Thomas,
> > No, that command line is good. You just hit a bug: I only tested the
> > emulation with the default SCSI ID 0 so far (i.e. I was using the
> > --scsi parameter without "1="), and apparently I forgot to set the
> > selected SCSI ID in one of the many variables. Should be fixed now!
> > Note that the SCSI code is is a "marriage" of Hatari's SCSI command
> > emulation layer (that has only been used for ACSI so far), with the
> > NCR5380 and SCSI bus state emulation code from WinUAE. It already
> > took quite a while to make them play nice together, so you likely
> > have to expect some more oddities here. Did I already mention that
> > it is still "experimental" ;-) ?
> That's what I guessed :-). Anyway, the drive image is now detected by
> HDDRUTIL, but there are some issues with the emulation, which prevent
> me from using the image.
> When running SDRVTEST (available for download on
> https://www.hddriver.net/en/downloads.html) it reported some problems
> with the emulation, please see the attached log.
Ok, thanks a lot for the hint, I think I've found and fixed the bug with
the unsupported commands now. SDRVTEST now reports "OK" for a SCSI drive
attached with ID 0.
There still seem to be some problems with IDs > 0, though. E.g. with
https://www.hddriver.net/downloads/hddrdemo101_big_endian.img the driver is
initially loaded, but then fails to recognize the partition table. Do
you know what could be wrong here?