From: Niklas Cassel <cassel@kernel.org>
To: Philip Pemberton <lists@philpem.me.uk>
Cc: linux-ide@vger.kernel.org
Subject: Re: Zip 100 ATAPI not working, "qc timeout" and "failed to clear UNIT ATTENTION"
Date: Wed, 19 Feb 2025 17:02:38 +0100 [thread overview]
Message-ID: <Z7YAnqGsrWSzBirf@ryzen> (raw)
In-Reply-To: <Z7X9aPpgBjNln9CJ@ryzen>
On Wed, Feb 19, 2025 at 04:48:56PM +0100, Niklas Cassel wrote:
>
> Perhaps your could try with something like:
>
> diff --git a/drivers/ata/libata-eh.c b/drivers/ata/libata-eh.c
> index 3b303d4ae37a..bc2a317c97da 100644
> --- a/drivers/ata/libata-eh.c
> +++ b/drivers/ata/libata-eh.c
> @@ -1543,7 +1543,7 @@ unsigned int atapi_eh_request_sense(struct ata_device *dev,
> tf.command = ATA_CMD_PACKET;
>
> /* is it pointless to prefer PIO for "safety reasons"? */
> - if (ap->flags & ATA_FLAG_PIO_DMA) {
> + if (0) {
> tf.protocol = ATAPI_PROT_DMA;
> tf.feature |= ATAPI_PKT_DMA;
> } else {
>
> To see if NOT using DMA for PIO cmds makes any difference.
Or the big hammer:
diff --git a/drivers/ata/ahci.h b/drivers/ata/ahci.h
index 8e895ae45c86..920462101775 100644
--- a/drivers/ata/ahci.h
+++ b/drivers/ata/ahci.h
@@ -249,7 +249,7 @@ enum {
/* ap->flags bits */
- AHCI_FLAG_COMMON = ATA_FLAG_SATA | ATA_FLAG_PIO_DMA |
+ AHCI_FLAG_COMMON = ATA_FLAG_SATA |
ATA_FLAG_ACPI_SATA | ATA_FLAG_AN,
ICH_MAP = 0x90, /* ICH MAP register */
Just make sure to not use this on any system other than the machine that
you are debugging on.
Kind regards,
Niklas
next prev parent reply other threads:[~2025-02-19 16:02 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
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 [this message]
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=Z7YAnqGsrWSzBirf@ryzen \
--to=cassel@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.