On Tue, 1 Nov 2016, Michael Schmitz wrote:
> Hi Finn,
>
> Am 01.11.2016 um 12:47 schrieb Finn Thain:
> >
> > On Tue, 1 Nov 2016, Michael Schmitz wrote:
> >
> >>> I had tried to set that bit in zorro_esp_slave_configure but had not
> >>> done a proper job of it - I'd only set esp->config3 and
Hi Finn,
Am 01.11.2016 um 12:47 schrieb Finn Thain:
>
> On Tue, 1 Nov 2016, Michael Schmitz wrote:
>
>>> I had tried to set that bit in zorro_esp_slave_configure but had not
>>> done a proper job of it - I'd only set esp->config3 and forgot to set
>>> tp->esp_config3. Time to retest this ...
>
On Tue, 1 Nov 2016, Michael Schmitz wrote:
> > I had tried to set that bit in zorro_esp_slave_configure but had not
> > done a proper job of it - I'd only set esp->config3 and forgot to set
> > tp->esp_config3. Time to retest this ...
>
> I don't think it's quite that easy - the ESP_CONFIG3_TE
Hi Finn,
> I had tried to set that bit in zorro_esp_slave_configure but had not
> done a proper job of it - I'd only set esp->config3 and forgot to set
> tp->esp_config3. Time to retest this ...
I don't think it's quite that easy - the ESP_CONFIG3_TENB bit needs to
be set for all targets if at le
Hi Finn,
Am 30.10.2016 um 15:33 schrieb Finn Thain:
>
> On Sat, 29 Oct 2016, I wrote:
>
>>
>> On Sun, 13 Apr 2014, David Miller wrote:
>>
>>>
>>> But oddly in the NCR53CX docs:
>>>
>>>
>>> http://www.ibiblio.org/pub/historic-linux/early-ports/Sparc/NCR/NCR53C9X.txt
>>>
>>> it speaks as if E
On Sat, 29 Oct 2016, I wrote:
>
> On Sun, 13 Apr 2014, David Miller wrote:
>
> >
> > 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
> >
On Sun, 13 Apr 2014, David Miller wrote:
> > esp_get_revision but later cleared in the same function. It appears
> > we'd need to set it after the call to scsi_esp_register() - can you
> > test whether that obsoletes the zorro_esp_slave_configure hack,
> > Tuomas?
> ...
> > > Group 2 Commands
Hi Geert,
> [sorry for the long delay]
Tell me about it :-) I haven't had a good idea how to address this
problem so rather kept mum about it.
> On Mon, Apr 14, 2014 at 10:51 AM, Michael Schmitz
> wrote:
>> Not sure my patch had ever made it into Geert's m68k-queue - except for the
>> patch in
Hi Michael,
[sorry for the long delay]
On Mon, Apr 14, 2014 at 10:51 AM, Michael Schmitz wrote:
> Not sure my patch had ever made it into Geert's m68k-queue - except for the
> patch in my previous mail, my zorro_esp.c is still the same as I got from
> you in October last year. The project has be
On 14.04.2014 12:01, Michael Schmitz wrote:
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_T
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 b
Hi Tuomas,
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
On 14.04.2014 05:14, David Miller wrote:
From: Michael Schmitz
Date: Mon, 14 Apr 2014 10:38:09 +1200
That appears to be our problem if I recall correctly Tuomas' debugging
report. (reselection, not selection as initiator). As
esp_slave_configure() enables queue tags regardless of chip config,
From: Michael Schmitz
Date: Mon, 14 Apr 2014 10:38:09 +1200
> That appears to be our problem if I recall correctly Tuomas' debugging
> report. (reselection, not selection as initiator). As
> esp_slave_configure() enables queue tags regardless of chip config,
> we'd best make certain the chip is c
Hi Kars,
thanks for the PDFs!
> Bit 2 SCSI-2
>
> Setting this bit allows the FSC to support two new features adopted in
> SCSI-2: the 3-byte message exchange for Tagged-Queueing and Group 2
> commands. These features can also be set independently in the Config 3
> register.
>
> Tagged-Queueing
>
Hi Michael,
2014-04-11 3:47 GMT+02:00 Michael Schmitz :
> The more important issue is the one about the one-byte reconnect
> message. Does the manual speak to that particular issue? Any hint on
> how we could enable SCSI-2 features on chip init?
There's the SCSI2 bit in the Config 2 register and
Hello Kars,
>> > 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 haven't gone far enough back i
2014-04-06 22:33 GMT+02:00 Michael Schmitz :
>
> Hello Dave, Tuomas,
>
> >> 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 chi
From: Michael Schmitz
Date: Mon, 7 Apr 2014 08:33:12 +1200
> Hello Dave, Tuomas,
>
>>> 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
Hello Dave, Tuomas,
>> 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 com
From: Tuomas Vainikka
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
Tuomas,
I might still have a copy of the manual somewhere from way back, if you
haven't found it anywhere. Would be on an old disk or even hardcopy in
storage, so please confirm you still need it.
Cheers,
Michael
Am 13.09.2013 um 03:36 schrieb Tuomas Vainikka:
On 09/11/2013 05:48 PM, G
On 09/11/2013 05:48 PM, Geert Uytterhoeven wrote:
On Wed, Sep 11, 2013 at 12:12 PM, Michael Schmitz wrote:
problem. Using PIO, only the first byte of the tag message comes through. It
might not be esp_scsi's fault, but there seems to be an assumption that all
devices support TCQ. Also, no SCSI-
23 matches
Mail list logo
