All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Campbell <brad@wasp.net.au>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH] libata ATA vs SATA detection and workaround.
Date: Mon, 30 Aug 2004 18:42:36 +0400	[thread overview]
Message-ID: <41333CDC.5040106@wasp.net.au> (raw)
In-Reply-To: <41321F7F.7050300@pobox.com>

[-- Attachment #1: Type: text/plain, Size: 1378 bytes --]

Jeff Garzik wrote:
> Jeff Garzik wrote:
> 
>> me either, unless I can figure out a way to detect that a disk is PATA 
>> not SATA.  Nothing is obvious from the specs on www.t13.org, but who 
>> knows.
> 
> 
> According to the Serial ATA docs, IDENTIFY DEVICE word 93 will be zero 
> if it's Serial ATA.  Who knows if that's true, given the wierd wild 
> world of ATA devices.
> 

I'm assuming here that if the driver uses sata_phy_reset in libata-core then it's actually a SATA 
controller.

Patch attached, tested and verified.
SATA drives (of which I only have one brand) report IDENTIFY DEVICE word 93 as zero, ATA devices 
behind the bridge (Of which I only have one brand) report at a minimum bit 13 to report an 80 
conductor cable.

Like I said before, my assumptions are

A) IDENTIFY DEVICE and the associated Word 93 register have been *Mandatory* at least since ATA-5

B) ATA-5 maxed out at < udma/100 and did not contain lba48

C) The SATA->PATA bridge looks like an 80 conductor cable and thus on any drive that supports lba48 
will always present a non-zero value in IDENTIFY DEVICE Word 93.

It works here anyway.
Patch against vanilla 2.6.9-rc1 attached (including your ata.h patch)

Thanks again for all the help. I'll see if I can get some other older ATA drives to test with (I 
might have to gut all the machines in the office for the weekend)

Regards,
Brad

[-- Attachment #2: diff --]
[-- Type: text/plain, Size: 1520 bytes --]

diff -ur orig/linux-2.6.0/drivers/scsi/libata-core.c linux-2.6.9-rc1/drivers/scsi/libata-core.c
--- orig/linux-2.6.0/drivers/scsi/libata-core.c	2004-08-30 18:31:31.000000000 +0400
+++ linux-2.6.9-rc1/drivers/scsi/libata-core.c	2004-08-30 18:22:05.000000000 +0400
@@ -1152,6 +1152,16 @@
 			found = 1;
 			if (ap->ops->dev_config)
 				ap->ops->dev_config(ap, &ap->device[i]);
+			/* limit bridge transfers to udma5, 200 sectors */
+			printk("Value is %u\n",ap->cbl==ATA_CBL_SATA);
+			if ((ap->cbl == ATA_CBL_SATA) && (!ata_id_is_sata(ap->device))) {
+				printk(KERN_INFO "ata%u(%u): applying bridge limits\n",
+					ap->id, ap->device->devno);
+				ap->udma_mask &= ATA_UDMA5;
+				ap->host->max_sectors = ATA_MAX_SECTORS;
+				ap->host->hostt->max_sectors = ATA_MAX_SECTORS;
+				ap->device->flags |= ATA_DFLAG_LOCK_SECTORS;
+			}
 		}
 	}
 
@@ -1226,7 +1236,7 @@
 		ata_port_disable(ap);
 		return;
 	}
-
+	ap->cbl = ATA_CBL_SATA;
 	ata_bus_reset(ap);
 }
 
diff -ur orig/linux-2.6.0/include/linux/ata.h linux-2.6.9-rc1/include/linux/ata.h
--- orig/linux-2.6.0/include/linux/ata.h	2004-08-30 18:31:32.000000000 +0400
+++ linux-2.6.9-rc1/include/linux/ata.h	2004-08-30 17:56:53.000000000 +0400
@@ -218,6 +218,7 @@
 };
 
 #define ata_id_is_ata(dev)	(((dev)->id[0] & (1 << 15)) == 0)
+#define ata_id_is_sata(dev)	((dev)->id[93] == 0)
 #define ata_id_rahead_enabled(dev) ((dev)->id[85] & (1 << 6))
 #define ata_id_wcache_enabled(dev) ((dev)->id[85] & (1 << 5))
 #define ata_id_has_flush(dev) ((dev)->id[83] & (1 << 12))

  parent reply	other threads:[~2004-08-30 14:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-29 17:09 libata dev_config call order wrong Brad Campbell
2004-08-29 17:29 ` Jeff Garzik
2004-08-29 17:47   ` Brad Campbell
2004-08-29 17:59     ` Jeff Garzik
2004-08-29 18:25       ` Jeff Garzik
2004-08-29 18:59         ` Alan Cox
2004-08-30  9:12           ` Brad Campbell
2004-08-30 13:22             ` Alan Cox
2004-08-30 14:38               ` Brad Campbell
2004-08-30 14:42         ` Brad Campbell [this message]
2004-08-30 14:57           ` [PATCH] libata ATA vs SATA detection and workaround Brad Campbell
2004-08-30 14:57             ` Brad Campbell
2004-08-30 16:06             ` Jeff Garzik
2004-08-30 16:34               ` Brad Campbell
2004-08-30 16:37                 ` Jeff Garzik
2004-08-30 17:17                   ` Brad Campbell
2004-08-30 17:59                     ` Jeff Garzik
2004-08-31  7:47                       ` Brad Campbell

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=41333CDC.5040106@wasp.net.au \
    --to=brad@wasp.net.au \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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.