From: Michael Schmitz <schmitzmic@gmail.com>
To: Vainikka Tuomas <tuomas.vainikka@aalto.fi>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k <linux-m68k@vger.kernel.org>
Subject: Re: m68k v3.16 status update
Date: Fri, 15 Dec 2017 07:40:07 +1300 [thread overview]
Message-ID: <CAOmrzkJJXZb153ig=d=Cywr59hid7X3UJvUD-wgtYtZm7KsCuQ@mail.gmail.com> (raw)
In-Reply-To: <4403d779c1664692ae5a7ef5b69ec888@aalto.fi>
Hi Tuomas,
fair enough - I'll get the PIO code tested by forcing PIO transfers on
elgar, and submit the driver for review once that's done. Maybe
someone else has a chance to test the fix in the meantime.
Cheers,
Michael
On Fri, Dec 15, 2017 at 1:07 AM, Vainikka Tuomas
<tuomas.vainikka@aalto.fi> wrote:
> Hello,
>
> I do have the hardware, but unfortunately I do not have the time to test it.
>
> -Tuomas
> ________________________________________
> From: linux-m68k-owner@vger.kernel.org <linux-m68k-owner@vger.kernel.org> on behalf of Michael Schmitz <schmitzmic@gmail.com>
> Sent: 14 December 2017 06:47
> To: Tuomas Vainikka
> Cc: Geert Uytterhoeven; linux-m68k
> Subject: Re: m68k v3.16 status update
>
> Tuomas,
>
> are you still in the position to test tagged queue messages on Zorro ESP
> hardware?
>
> I've modified the Zorro ESP driver based on the work Finn Thain did for
> the Mac ESP driver (handling message in transfer by PIO, with special
> handshaking provisions for the message in case) and tried to test this
> on elgar (CyberStorm I ESP) but the original bug does not show up there.
> Might be to do with the SCSI disk used, or the CyberStorm I board.
>
> Might be better to test the new code on your hardware where we know the
> bug happened in the first place.
>
> Cheers,
>
> Michael
>
> Am 09.08.2014 um 18:45 schrieb Tuomas Vainikka:
>> On 09.08.2014 01:25, Michael Schmitz wrote:
>>> Hi Tuomas,
>>>>>
>>>>> There's still the Amiga Zorro ESP patch out in limbo - DaveM
>>>>> suggested a change to enable SCSI-2 features to help with extended
>>>>> message bytes but that did not work as intended. Haven't had time to
>>>>> follow that one up. Tuomas' fix to the driver to bypass DMA for
>>>>> message in works OK though - do you want it submitted back to
>>>>> linux-scsi as is, or wait for a perfect solution (pun on me ...)?
>>>>>
>>>>>
>>>> Just to refresh your memory, the final fix was not to bypass DMA at
>>>> any level (I did that for the command transfer, but that didn't
>>>> help), but to have a dedicated slave_configure() function in the
>>>> Amiga Zorro ESP driver that would not enable TCQ.
>>>
>>> You guessed right about memory failing me - it wasn't about DMA in the
>>> end (for some reason, I seem to have DMA stuck in my mind at the
>>> moment), Do you see any other avenues to try and enable tagged
>>> commands in the ESP chip? We tried one config register only so far...
>>>
>> I think I've tested almost all possible register settings for the chip,
>> but it occurred to me that it is not enough to enable some chip features
>> by flipping bits. The code in esp_scsi would need to be modified to
>> handle the behaviour of these enabled features also.
>>
>> So, rethinking the code in esp_scsi would be one option.
>>
>> The second possibility is that I have a buggy chip in my setup. Removing
>> a sticker from my SCSI-board revealed the chip to be an AMD AM53CF94.
>> There are different versions of the SCSI-boards out there with different
>> chips; NCR, AMD, and QLogic, so if we had more people testing the driver
>> we would find out if the chip is actually the problem. (Is anyone even
>> testing the ISA/PCI cards that use esp_scsi?)
>>
>> Those are my suggestions at the TCQ problem.
>>
>> But do we really need TCQ?
>>
>> -Tuomas
> --
> To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-12-14 18:40 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 19:40 m68k v3.16 status update Geert Uytterhoeven
2014-08-05 19:52 ` Ingo Jürgensmann
2014-08-05 20:29 ` John Paul Adrian Glaubitz
2014-08-06 7:35 ` Geert Uytterhoeven
2014-08-06 9:53 ` John Paul Adrian Glaubitz
2014-08-08 8:58 ` Michael Schmitz
2014-08-08 9:53 ` Tuomas Vainikka
2014-08-08 8:38 ` Michael Schmitz
2014-08-08 9:45 ` Christian T. Steigies
2014-08-08 22:33 ` Michael Schmitz
2014-08-08 14:25 ` Tuomas Vainikka
2014-08-08 22:25 ` Michael Schmitz
2014-08-09 6:45 ` Tuomas Vainikka
2014-08-10 1:44 ` Michael Schmitz
2017-12-14 4:47 ` Michael Schmitz
2017-12-14 12:07 ` Vainikka Tuomas
2017-12-14 13:20 ` John Paul Adrian Glaubitz
2017-12-14 18:40 ` Michael Schmitz [this message]
2017-12-14 23:49 ` Finn Thain
2017-12-19 0:40 ` Michael Schmitz
2017-12-19 3:35 ` Finn Thain
2017-12-19 6:11 ` Michael Schmitz
2017-12-19 22:06 ` zorro_esp, was " Finn Thain
2017-12-19 23:01 ` Finn Thain
2017-12-20 1:42 ` Michael Schmitz
2017-12-20 3:34 ` Finn Thain
2017-12-28 8:02 ` Michael Schmitz
2017-12-29 0:02 ` Finn Thain
2017-12-29 9:09 ` Michael Schmitz
2017-12-19 8:19 ` Geert Uytterhoeven
2017-12-20 7:33 ` zorro_esp, was: " Michael Schmitz
2017-12-20 8:13 ` Geert Uytterhoeven
2017-12-15 8:34 ` Vainikka Tuomas
2017-12-16 0:04 ` TCQ with zorro_esp, was " Finn Thain
2017-12-19 0:44 ` Michael Schmitz
2014-08-09 1:14 ` Michael Schmitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOmrzkJJXZb153ig=d=Cywr59hid7X3UJvUD-wgtYtZm7KsCuQ@mail.gmail.com' \
--to=schmitzmic@gmail.com \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=tuomas.vainikka@aalto.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).