From: David Miller <davem@davemloft.net>
To: tuomas.vainikka@aalto.fi
Cc: geert@linux-m68k.org, schmitzmic@gmail.com,
linux-m68k@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: esp_scsi QTAG in FAS216
Date: Fri, 04 Apr 2014 16:28:30 -0400 (EDT) [thread overview]
Message-ID: <20140404.162830.1700547572091852195.davem@davemloft.net> (raw)
In-Reply-To: <5231DF69.6070807@aalto.fi>
From: Tuomas Vainikka <tuomas.vainikka@aalto.fi>
Date: Thu, 12 Sep 2013 18:36:09 +0300
> Does anyone have the register descriptions for the FAS216 chip? It
> would seem that receiving only one byte during reconnect is perfectly
> normal [1] unless SCSI-2 features are explicitly enabled (which
> esp_scsi doesn't seem to be doing).
This is quite possibly true. I've never see it happen myself while
testing the driver though.
> Also, looking at the timeout formulae in the old NCR53C9x.c driver,
> the values would be different for FAS216. Why was this dropped from
> the modern esp_scsi?
I've never seen a formula for any ESP or FAS chip for the timeout
other than the one mentioned in huge comment in
esp_set_clock_params(), although I do see the 7668 instead of 8192
factor being used in the old NCR53C9x driver.
I wrote esp_scsi.c based upon the old sparc ESP driver and the docs
I had available to me.
next prev parent reply other threads:[~2014-04-04 20:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1370552199-15048-1-git-send-email-schmitz@debian.org>
[not found] ` <520D4AE3.6040801@aalto.fi>
[not found] ` <520E76FC.9040803@aalto.fi>
[not found] ` <11425cb5ec432e2fbb7b675052e8b33d@gmail.com>
[not found] ` <520F5F81.7090409@aalto.fi>
[not found] ` <52102BEC.7000006@gmail.com>
[not found] ` <CAMuHMdV9vP-Qg2my5fyT+pa_WcDfZAPx5T1-4kXP8eD1oL8Kog@mail.gmail.com>
[not found] ` <52108CAF.1010700@gmail.com>
[not found] ` <CAMuHMdWqNBjHKiDojPdjzuOV65QXzjeMX5VbtUvgU7VTP4iYFg@mail.gmail.com>
[not found] ` <5211DBD8.5090801@gmail.com>
[not found] ` <5212840A.4080300@aalto.fi>
[not found] ` <1ef2d87e4efecb2d8c8c2eaf8ac5fd51@gmail.com>
[not found] ` <52133E48.50501@aalto.fi>
[not found] ` <CAOmrzkKtB4OpnFNFh9PR4V8bc3ExfFXpwtkhGj0veQ4w-d=cqA@mail.gmail.com>
[not found] ` <522F8B67.2080603@aalto.fi>
[not found] ` <CAOmrzkKP4YcvnHcrtucMvS9WSaeg+6-qnobOWN6hBK=wkUHemg@mail.gmail.com>
[not found] ` <CAMuHMdUH=9sv-Vb3ZTAGyfvEQOO0x0x1cUYhfd7040k8d+bSYg@mail.gmail.com>
2013-09-12 15:36 ` esp_scsi QTAG in FAS216 (was Re: [PATCH 0/2] Experimental Amiga Zorro ESP driver) Tuomas Vainikka
2013-09-26 13:50 ` Michael Schmitz
2014-04-04 20:28 ` David Miller [this message]
2014-04-06 20:33 ` esp_scsi QTAG in FAS216 Michael Schmitz
2014-04-07 3:39 ` David Miller
2014-04-10 14:31 ` Kars de Jong
2014-04-11 1:47 ` Michael Schmitz
2014-04-13 14:47 ` Kars de Jong
2014-04-13 22:38 ` Michael Schmitz
2014-04-14 2:14 ` David Miller
2014-04-14 5:05 ` Tuomas Vainikka
2014-04-14 8:51 ` Michael Schmitz
2014-05-25 8:56 ` Geert Uytterhoeven
2014-05-26 1:15 ` Michael Schmitz
2014-04-14 9:01 ` Michael Schmitz
2014-05-04 11:41 ` Tuomas Vainikka
2016-10-28 21:54 ` Finn Thain
2016-10-30 2:33 ` Finn Thain
2016-10-31 8:03 ` Michael Schmitz
2016-10-31 18:54 ` Michael Schmitz
2016-10-31 23:47 ` Finn Thain
2016-11-01 7:09 ` Michael Schmitz
2016-11-01 7:23 ` Finn Thain
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=20140404.162830.1700547572091852195.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=schmitzmic@gmail.com \
--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).