public inbox for linux-ide@vger.kernel.org
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: Philip Pemberton <lists@philpem.me.uk>
Cc: Hannes Reinecke <hare@suse.de>, linux-ide@vger.kernel.org
Subject: Re: Zip 100 ATAPI not working, "qc timeout" and "failed to clear UNIT ATTENTION"
Date: Thu, 9 Jan 2025 14:22:21 +0100	[thread overview]
Message-ID: <Z3_NjZyXSL9ymjIF@ryzen> (raw)
In-Reply-To: <8d8be593-51c5-4029-b310-a0d9082f5eaa@philpem.me.uk>

On Thu, Jan 09, 2025 at 11:33:11AM +0000, Philip Pemberton wrote:
> On 09/01/2025 07:17, Hannes Reinecke wrote:
> > Which makes me wonder: does the SATA-to-PATA support ATAPI? It has been
> > removed from recent ATA specifications, so there's a chance the bridge
> > simply doesn't implement it ...
> 
> It seems to -- if I use the SATA-to-PATA adapter to put the drive in the
> Knoppix PC, the Zip drive works fine.

Which SATA-to-PATA adapter are you using?


Perhaps that computer (which was running a v3.x kernel) is using a different
SATA controller/driver, which has better ATAPI support?


Do you have the:
[ 4465.218535] ata3.00: ATAPI: IOMEGA  ZIP 100       ATAPI, 12.A, max 
PIO3, CDB intr, DMADIR
[ 4465.225787] ata3.00: configured for PIO0

prints from that other PC running v3.x kernel?


E.g. DMADIR can be automatically detected, if it is needed based on the
returned data in the IDENTIFY PACKET response, see:
https://www.mail-archive.com/linux-ide@vger.kernel.org/msg16469.html
https://www.spinics.net/lists/linux-ide/msg01514.html

The DMADIR print will only be there if we send an explicit DMA direction
with each command.

It would be interesting to see if it was there on your older kernel.

Also your device seems to only indicate support for PIO3, thus we see it
being configured for PIO. Thus, it seems that you are using PIO instead
of DMA. I think that DMADIR only matters when using a DMA mode and not PIO.

Forcing DMADIR=1 when your device only supports PIO, feels wrong to me,
but perhaps I am missing something. Also, why is your device only being
configured for PIO0 when it seems to support up to PIO3 speeds? Bug?


E.g. my print when using QEMU + ATAPI:
[    0.647370] ata2: SATA max UDMA/133 abar m4096@0xfebd2000 port 0xfebd2180 irq 90 lpm-pol 0
[    0.966896] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    0.971060] ata2.00: ATAPI: QEMU DVD-ROM, 2.5+, max UDMA/100
[    0.971818] ata2.00: applying bridge limits
[    0.972918] ata2.00: configured for UDMA/100
shows that the device supports up to UDMA/100, and later we also see that
we configure it for that speed.



Kind regards,
Niklas

  reply	other threads:[~2025-01-09 13:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-08 12:52 Zip 100 ATAPI not working, "qc timeout" and "failed to clear UNIT ATTENTION" Philip Pemberton
2025-01-08 13:42 ` Niklas Cassel
2025-01-08 13:45   ` Niklas Cassel
2025-01-09 11:36   ` Philip Pemberton
2025-01-08 14:05 ` Niklas Cassel
2025-01-09  7:17   ` Hannes Reinecke
2025-01-09 11:33     ` Philip Pemberton
2025-01-09 13:22       ` Niklas Cassel [this message]
2025-01-09 15:06         ` Philip Pemberton
2025-01-09 11:35   ` Philip Pemberton
     [not found]   ` <e1985151-c206-4be1-91c1-92eac16f6236@philpem.me.uk>
2025-01-09 12:22     ` Niklas Cassel
2025-01-09 15:31       ` Philip Pemberton
2025-01-17 13:37         ` Niklas Cassel
2025-01-23 13:19           ` Philip Pemberton
2025-01-23 16:19           ` Philip Pemberton
2025-01-24 10:03             ` Niklas Cassel
2025-02-18  3:05               ` Philip Pemberton
2025-02-19 15:48                 ` Niklas Cassel
2025-02-19 16:02                   ` Niklas Cassel
2025-02-19 20:04                     ` Philip Pemberton
2025-02-21  1:57                       ` Niklas Cassel
2025-02-21 17:08                         ` Philip Pemberton
2025-02-21 17:24                           ` Niklas Cassel

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=Z3_NjZyXSL9ymjIF@ryzen \
    --to=cassel@kernel.org \
    --cc=hare@suse.de \
    --cc=linux-ide@vger.kernel.org \
    --cc=lists@philpem.me.uk \
    /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