From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Clem Taylor <clemtaylor@comcast.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Any news on a higher performance sata_sil SIL_QUIRK_MOD15WRITE workaround?
Date: Thu, 12 Aug 2004 21:37:04 +0100 [thread overview]
Message-ID: <1092343024.22513.69.camel@localhost.localdomain> (raw)
In-Reply-To: <20040812210345.GA9558@havoc.gtf.org>
On Iau, 2004-08-12 at 22:03, Jeff Garzik wrote:
> '15 or less' limit works, but 'sectors % 15 == 1' still produces odd
> Data FIS sizes that confuse Seagate drives.
>
> I thought you were saying that 'sectors % 15 == 1' was OK.
Only the subset of use I tried in siimage. Thats the 15 or less limit on
the specific list of seagate drives affected.
next prev parent reply other threads:[~2004-08-12 21:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 5:16 Any news on a higher performance sata_sil SIL_QUIRK_MOD15WRITE workaround? Clem Taylor
2004-08-12 6:43 ` Jeff Garzik
2004-08-12 12:00 ` Alan Cox
2004-08-12 15:16 ` Jeff Garzik
2004-08-12 19:59 ` Alan Cox
2004-08-12 21:03 ` Jeff Garzik
2004-08-12 20:37 ` Alan Cox [this message]
2004-08-13 4:18 ` Clem Taylor
2004-08-13 12:13 ` Alan Cox
2004-08-16 18:49 ` Eric Mudama
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=1092343024.22513.69.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=clemtaylor@comcast.net \
--cc=jgarzik@pobox.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox