All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Paul Jakma <paul@clubi.ie>
Cc: linux-ide@vger.kernel.org, Ricky Beam <jfbeam@bluetronic.net>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fix sata_sil quirk
Date: Tue, 22 Jun 2004 23:51:49 -0400	[thread overview]
Message-ID: <40D8FE55.3030008@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.60.0406230442410.2702@fogarty.jakma.org>

Paul Jakma wrote:
> On Tue, 22 Jun 2004, Jeff Garzik wrote:
> 
>> Cool.  Yeah, non-Seagate should be full speed and unaffected...
> 
> 
> But I got the impression your patch enables mod15-quirk for all LBA48 
> drives, is that correct? If so, if I have to update kernels here, I 
> think I'll reverse that one if it affects all LBA48, as I'd rather not 
> suffer the performance hit (its slow enough already because of slow 
> CPU/chipset/contended PCI bus thank you very much ;) ) - until such time 
> as a better fix is known.


Nope, my patch only enables ATA_DFLAG_LOCK_SECTORS for devices flagged 
with SIL_QUIRK_MOD15WRITE:

         { "ST320012AS",         SIL_QUIRK_MOD15WRITE },
         { "ST330013AS",         SIL_QUIRK_MOD15WRITE },
         { "ST340017AS",         SIL_QUIRK_MOD15WRITE },
         { "ST360015AS",         SIL_QUIRK_MOD15WRITE },
         { "ST380023AS",         SIL_QUIRK_MOD15WRITE },
         { "ST3120023AS",        SIL_QUIRK_MOD15WRITE },
         { "ST340014ASL",        SIL_QUIRK_MOD15WRITE },
         { "ST360014ASL",        SIL_QUIRK_MOD15WRITE },
         { "ST380011ASL",        SIL_QUIRK_MOD15WRITE },
         { "ST3120022ASL",       SIL_QUIRK_MOD15WRITE },
         { "ST3160021ASL",       SIL_QUIRK_MOD15WRITE },
         { "Maxtor 4D060H3",     SIL_QUIRK_UDMA5MAX },
[...]
         if (quirks & SIL_QUIRK_MOD15WRITE) {
                 printk(KERN_INFO "ata%u(%u): applying errata fix\n",
                        ap->id, dev->devno);
                 ap->host->max_sectors = 15;
                 ap->host->hostt->max_sectors = 15;
                 dev->flags |= ATA_DFLAG_LOCK_SECTORS;
                 return;
         }

  reply	other threads:[~2004-06-23  3:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-22 20:22 [PATCH] fix sata_sil quirk Jeff Garzik
2004-06-22 20:29 ` Ricky Beam
2004-06-22 20:29   ` Ricky Beam
2004-06-22 20:41   ` Jeff Garzik
2004-06-22 22:12   ` Jeff Garzik
2004-06-23  0:34     ` Ricky Beam
2004-06-23  0:34       ` Ricky Beam
2004-06-23  3:24 ` Paul Jakma
2004-06-23  3:39   ` Jeff Garzik
2004-06-23  3:46     ` Paul Jakma
2004-06-23  3:51       ` Jeff Garzik [this message]
2004-06-23  6:34         ` Ricky Beam
2004-06-23  6:34           ` Ricky Beam
2004-06-28  1:54           ` George Georgalis
2004-09-27  3:40             ` George Georgalis

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=40D8FE55.3030008@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=jfbeam@bluetronic.net \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@clubi.ie \
    /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.