From: Tejun Heo <htejun@gmail.com>
To: Jeff Breidenbach <jeff@jab.org>
Cc: Mark Lord <liml@rtr.ca>,
linux-ide@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Robert Hancock <hancockr@shaw.ca>,
Mikael Pettersson <mikpe@it.uu.se>, Jeff Garzik <jeff@garzik.org>
Subject: Re: stable basic 4-port SATA card
Date: Thu, 15 Nov 2007 16:58:50 +0900 [thread overview]
Message-ID: <473BFC3A.6010006@gmail.com> (raw)
In-Reply-To: <e03b90ae0711142337x7112904ar8673f08a19a6ff19@mail.gmail.com>
Jeff Breidenbach wrote:
> Thanks for the excellent rundown.
>
>> 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.
>
> I'm still a little confused how to translate this known-good chipset to
> an actual buyable PCI card. It isn't obvious from basic web searching.
That I don't know either. I usually magnify the product photograph and
try to read the chip number (I know shapes of several chips so it's
easier for me) or call the manufacturer. Just ask for the PCI ID and
look it up in linux PCI IDs repository or modinfo result.
--
tejun
next prev parent reply other threads:[~2007-11-15 7:59 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
2007-11-15 4:18 ` Mark Lord
2007-11-15 7:37 ` Jeff Breidenbach
2007-11-15 7:58 ` Tejun Heo [this message]
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=473BFC3A.6010006@gmail.com \
--to=htejun@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hancockr@shaw.ca \
--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).