From: Robert Hancock <hancockr@shaw.ca>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Breidenbach <jeff@jab.org>,
linux-ide@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Mikael Pettersson <mikpe@it.uu.se>, Jeff Garzik <jeff@garzik.org>,
Mark Lord <liml@rtr.ca>
Subject: Re: stable basic 4-port SATA card
Date: Wed, 14 Nov 2007 22:16:04 -0600 [thread overview]
Message-ID: <473BC804.9030008@shaw.ca> (raw)
In-Reply-To: <473BBDBE.7060208@gmail.com>
Tejun Heo wrote:
> Jeff Breidenbach wrote:
>> I read with interest I. Straford's current trials and tribulations
>> with the Promise SATA300 TX4. Do people have a favorite
>> alternative to this card that plays well with Linux? I've read the
>> chipset compatibility list, but am not sure how to boil that
>> information down to an actual buyable SATA controller.
>>
>> http://www.mail-archive.com/linux-ide@vger.kernel.org/msg12398.html
>> http://linux-ata.org/driver-status.html
>
> It's a sort of a difficult question to answer but I think it'll be nice
> to develop a standard answer to this kind of question and put it on
> linux-ata.org so that users can choose. It can also hopefully work as
> another pressure for vendors to enhance their linux support.
>
> Anyways, here are what I know.
>
> * ata_piix: Although it lacks shiny new features (interface limitation),
> it should work pretty well. No known serious bugs.
>
> * ahci: Well supported. Command switching PMP support is merged for
> 2.6.24 too. Many (if not most) vendors now use ahci as programming
> interface for storage controllers, so ahci driver supports lots of
> controllers from many vendors. Bugginess depends on which vendor or
> chip you're actually using but in general all are well supported and if
> you report a problem, it's very likely to get fixed soon.
>
> * sata_sil: 3112 chips have problem with early seagate drives but both
> 3112 itself and those drives have been discontinued for a long time now.
> There are reports of data corruption when 3114 is connected to mobos
> with NVidia chipsets. This is still being investigated. If you're on
> intel mobo, 3112/3114/3512 should work good.
>
> * sata_sil24: 3124/3132 chips don't have any outstanding serious
> problems. IRQ loss on PCI-X was the only recent serious known problem
> but it's fixed now. These chips are pretty advanced and all the
> advanced features are supported by Linux including FIS switching PMP
> support (will be included in 2.6.24 release); however, there is a known
> hardware performance limitation so you can't use full SATA bandwidth
> even if you use PMP but it's more than sufficient for most cases and
> this chip is my personal favorite.
>
> * sata_promise: Generally works okay; however there are still some
> problems with recent 3Gbps chips. (Mikael, please pitch in)
>
> * sata_nv: Generally works okay but ADMA support still seems to have
> some problems (Robert?).
There aren't many in the way of specific known problems that aren't
worked around. There was a hotplug issue that was reported (kernel bug
8421), but only seems to happen on a certain revision of MSI Neo4
Platinum board so I suspect it's a board issue. Also there's the
ATAPI/>4GB RAM issue that's being debugged. But I haven't seen many
reports pointing to driver problems.
As far as the poster's question, these controllers are all built into
the chipset, so it's not really relevant to their issue..
>
> * sata_inic162x: Has half-working driver. We need more info from the
> vendor to proceed further. Stay away from it for now.
>
> * sata_via: Works okay. No known serious problems but the chip is
> quirky and not too dependable when errors occur.
>
> * marvell ones: I don't have much idea. Jeff? Mark?
>
next prev parent reply other threads:[~2007-11-15 4:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 6:39 stable basic 4-port SATA card Jeff Breidenbach
2007-11-15 3:32 ` Tejun Heo
2007-11-15 4:16 ` Robert Hancock [this message]
2007-11-15 4:18 ` Mark Lord
2007-11-15 7:37 ` Jeff Breidenbach
2007-11-15 7:58 ` Tejun Heo
2007-11-15 9:50 ` Jim Paris
2007-11-15 22:37 ` john
-- strict thread matches above, loose matches on Subject: below --
2007-11-15 10:01 Mikael Pettersson
2007-11-19 7:25 ` Tejun Heo
2007-12-13 13:37 ` Patric Karlsson
2007-12-13 14:09 ` Mikael Pettersson
2007-12-13 16:37 ` Krzysztof Oledzki
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=473BC804.9030008@shaw.ca \
--to=hancockr@shaw.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=jeff@jab.org \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=mikpe@it.uu.se \
/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).