From: Michael Schmitz <schmitzmic@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: linux-m68k@vger.kernel.org, geert@linux-m68k.org,
jongk@linux-m68k.org, tuomas.vainikka@aalto.fi,
linux-scsi@vger.kernel.org
Subject: Re: esp_scsi QTAG in FAS216
Date: Mon, 14 Apr 2014 21:01:02 +1200 [thread overview]
Message-ID: <0ee24dc77b71e282562b794aaa4039cd@gmail.com> (raw)
In-Reply-To: <20140413.221414.853080853067673824.davem@davemloft.net>
Hi Dave,
>>> When this bit is set, the 53CF94/96 can receive 3-byte messages
>>> during
>>> bus-initiated Select With ATN. This feature is also enabled by
>>> setting
>>> bit 3 in the Configuration 2 register.
>>
>> My preference would be to set this one (named ESP_CONFIG3_TBMS). Your
>> opinion, Dave?
>
> As seems to be agreed upon here, the SCSI2 bit in the CONFIG2 register
> (ESP_CONFIG2_SCSI2ENAB) is only for when the chip is used in target
> mode. So it is not relevant for our discussion because this driver is
> for initiator mode operation only.
Agreed. ESP_CONFIG2_SCSI2ENAB might do more than we intend, and have
unintended side effects. It's just easier to test whether this fixes
our problem.
>
> But some pieces of documentation seem like they might not agree on
> this point.
>
> With respect to bit 3 in the config3 register, it can take on one of
> two meaning depending upon chip revision. As per
> ESP_CONFIG3_{TMS,FCLK}
> it either controls fast SCSI clocking, or it enabled 3 byte message
> recognition.
>
> But oddly in the NCR53CX docs:
>
> http://www.ibiblio.org/pub/historic-linux/early-ports/Sparc/NCR/
> NCR53C9X.txt
>
> it speaks as if ESP_CONFIG3_TMS and ESP_CONFIG3_TENB are merely finer
> grained versions of config2 register setting ESP_CONFIG2_SCSI2ENAB,
> which enables both features.
That's what I understood from the bits Kars quoted, yes. And in the
Amiga driver cases, it will always be the 3 byte message feature
controlled by that bit, as far as I can see.
>
> Again I looked at the FreeBSD driver and for all chips after plain
> esp100, they set ESP_CONFIG2_SCSI2ENAB.
>
> Can we try testing the following patch?
That would be even easier than setting it explicitly in the Zorro
driver, thanks,
Michael
>
> ====================
> esp_scsi: Set SCSI2 bit in config2 register.
>
> This should allow proper recognition of 3 byte reselection
> on all esp100a and later chips.
>
> Reported-by: Kars de Jong <jongk@linux-m68k.org>
> Reported-by: Michael Schmitz <schmitzmic@gmail.com>
> Signed-off-by: David S. Miller <davem@davemloft.net>
>
> diff --git a/drivers/scsi/esp_scsi.c b/drivers/scsi/esp_scsi.c
> index 55548dc..16f69e0 100644
> --- a/drivers/scsi/esp_scsi.c
> +++ b/drivers/scsi/esp_scsi.c
> @@ -2160,7 +2160,7 @@ static void esp_get_revision(struct esp *esp)
> */
> esp->rev = ESP100;
> } else {
> - esp->config2 = 0;
> + esp->config2 = ESP_CONFIG2_SCSI2ENAB;
> esp_set_all_config3(esp, 5);
> esp->prev_cfg3 = 5;
> esp_write8(esp->config2, ESP_CFG2);
> @@ -2187,8 +2187,6 @@ static void esp_get_revision(struct esp *esp)
> } else {
> esp->rev = ESP236;
> }
> - esp->config2 = 0;
> - esp_write8(esp->config2, ESP_CFG2);
> }
> }
> }
next prev parent reply other threads:[~2014-04-14 9:01 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 ` esp_scsi QTAG in FAS216 David Miller
2014-04-06 20:33 ` 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 [this message]
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=0ee24dc77b71e282562b794aaa4039cd@gmail.com \
--to=schmitzmic@gmail.com \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=jongk@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-scsi@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).