On Mon, 31 Oct 2016, Michael Schmitz wrote:
> Am 30.10.2016 um 18:52 schrieb Finn Thain:
> >
> > On Sun, 30 Oct 2016, Michael Schmitz wrote:
> >
> > > but what makes the driver work with most disks but fail with some?
> > > Different SCSI command set supported by the disks?
> >
> > Anything t
Hi Geert,
brain fade. sorry. Meant to say - depending on chip revision bit 3
takes a different semantics.
And yes, this is getting a wee bit technical. I just don't think we're
close to anything fit for review on linux-scsi.
Cheers,
Mchael
On Mon, Oct 31, 2016 at 8:48 PM, Geert Uytterhoeven
On Mon, Oct 31, 2016 at 8:40 AM, Michael Schmitz wrote:
> What chip revision is this doc for? As far as I can make out, it should
> be fas100a? The esp_scsi.h comments suggest the tagged queuing bit is
> for revisions > fas236. The chips used on Macs were probably esp236 or
> fas236? Depending on
Hi Finn,
Am 30.10.2016 um 18:52 schrieb Finn Thain:
>
> On Sun, 30 Oct 2016, Michael Schmitz wrote:
>
>> but what makes the driver work with most disks but fail with some?
>> Different SCSI command set supported by the disks?
>
> Anything that would inhibit disconnection/reselection should avo
On Sun, 30 Oct 2016, Michael Schmitz wrote:
> but what makes the driver work with most disks but fail with some?
> Different SCSI command set supported by the disks?
Anything that would inhibit disconnection/reselection should avoid the
bug. (BTW ISTR that my SCSI2SD never disconnects a comman
Hi Finn,
>>
>> the problem with trying to read two tag bytes does sound familiar - I
>> believe we ran into that one (or a similar one) while trying to revive
>> the Amiga ESP drivers.
>>
>
> That's intriguing. I hadn't realised that those zorro_esp discussions on
> the mailing lists (linked b
6 matches
Mail list logo
