Kars,
Don't mess with CONFIG3 - we've tried all that, and in the end had to
use PIO to transfer message bytes. Problems with tagged queueing in
the ESP driver are usually all due to the DMA not transferring single
bytes on Amiga. The additional message byte required to see a reselect
for a tagged command complete remains stuck in the ESP fifo. Can't see
how this would be affected by the driver mis-identifying the chip as
FAS100A.
Regardig mis-detection of the chip revision - can you print the
'version' and 'family_code' variables in the esp->rev == FAST branch
of esp_reset_esp() please?
Can you also send the Zorro device ID data for your board, just so I
know which one of the Blizzard SCSI variants we are talking about
here?
Cheers,
Michael
On Tue, Oct 29, 2019 at 4:39 AM Kars de Jong <jongk@xxxxxxxxxxxxxx> wrote:
Op ma 28 okt. 2019 om 14:20 schreef John Paul Adrian Glaubitz
<glaubitz@xxxxxxxxxxxxxxxxxxx>:
On 10/28/19 2:00 PM, Kars de Jong wrote:
The new zorro_esp has seen a lot of rewrite. So old bugs might have been
fixed now.
Yes, for Mac support etc. Unfortunately it doesn't work for me. For
starters. it does not identify my chip correctly, it says it's a
FAS100A (it's actually a Symbios Logic 53CF94-2 which is more like a
FAS236).
But after I fixed that it still doesn't work.
It works perfectly fine with my Amiga 4000 and the SCSI controller on the
Cyberstorm: http://amiga.resource.cx/exp/cyberstorm1.
Michael actually tested everything on the Amiga 4000.
It probably uses a different chip. The text and images show it's a
QLogic FAS216 (which is the same as a FAS236, FAS236 is the
differential variant). The type should more accurately be presented as
"FAS2x6" since you can't tell which type it is in software.
Some of the bits in CONFIG3 have completely different meanings between
these chip variants, and because of the misdetection it is quite wrong
for the 53CF9x-2 in my A1200.
I will try out some things this evening, I naively added the FSC to
the end of the enum, but the code does things like "if (esp->rev >=
FAS100A)" which break horribly then.
It looks like it might work if I add my chip type between FAS236 and
FAS100A in the esp_rev enum.
Kind regards,
Kars.
