From: Eric Wong <eric@petta-tech.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: Silicon Image 3112 h/w docs available
Date: Sat, 23 Oct 2004 12:11:25 -0700 [thread overview]
Message-ID: <20041023191125.GJ9119@mail.petta-tech.com> (raw)
In-Reply-To: <41792BC3.9060304@pobox.com>
[-- Attachment #1: Type: text/plain, Size: 1342 bytes --]
Jeff Garzik <jgarzik@pobox.com> wrote:
>
> In order to better support open source developers, Silicon Image has
> been kind enough to give me permission to publicly post the hardware
> documentation for some of their older SATA chipsets on my docs site,
> namely the 3112 in this case:
>
> http://gkernel.sourceforge.net/specs/sii/3112A_SiI-DS-0095-B2.pdf.bz2
>
> This documentation will assist developers in maintaining the
> siimage/sata_sil SATA drivers in the Linux kernel.
>
> So now the 311x joins the ranks of "open hardware". Thanks, SiI!
Doesn't seem to contain any more info on drives/controllers affected by
the mod15write quirk. I'd like to see firmware revisions added to the
blacklist, and not just model numbers anymore. I didn't have that
information when I first implemented the blacklist (model numbers only),
and it still doesn't seem to be available right now.
I'm rather disappointed that the drive (ST3160023AS) I use has managed
to get its way onto the blacklist[1]. I'm using rev 3.05 of that drive
with a 3112 (rev 02), and have been for nearly a year at full speed and
have never had problems under heavy read/write usage. Setups affected
by an uncorrected mod15write bug are corrupted almost immediately, no?
--
Eric Wong -- eric@petta-tech.com -- normalperson@yhbt.net
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-23 19:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-22 15:48 Silicon Image 3112 h/w docs available Jeff Garzik
2004-10-23 19:11 ` Eric Wong [this message]
2004-10-25 17:53 ` 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=20041023191125.GJ9119@mail.petta-tech.com \
--to=eric@petta-tech.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).