linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sven Eschenberg <sven@whgl.uni-frankfurt.de>
To: linux-raid@vger.kernel.org
Subject: Re: Recommended pci-e 1x SATA cards.
Date: Sun, 17 Apr 2011 23:18:44 +0200	[thread overview]
Message-ID: <1303075124.2009.28.camel@HansWurst> (raw)
In-Reply-To: <4DAB4CF1.8050409@hardwarefreak.com>

Are you sure about this?

All those nifty specification updates for CPUs tell quite a different
story. And yes IC producers usually have such things too, they just
prefer to not publish them openly but rather decide to gag their
customers (like OEMs) by non disclosure agreements, if those plan on
getting a hold of those spec updates to work around the issues instead
of throwing away all the chips they bought.

But that just on a side note.

Bad PCB design and bad quality components are usually the more common
things causing problems. On the other hand, what was that story about
the ICHs in quite some chipsets having problems with the SATA Ports?

http://newsroom.intel.com/community/intel_newsroom/blog/2011/01/31/intel-identifies-chipset-design-error-implementing-solution

BTW: Big OEMs decided to get those broken chips nevertheless for
notebooks, because the problems usually do not occur with the first two
ports and the chips will probably be VERY cheap *eg*.

Marvell had issues (design) with the legacy PATA Interface on some
PATA/SATA chips earlier, then bumped the rev. and fixed the silicon.

Design errors and flaws are extremely common and there are certainly
enough in any IC, question is, if you hit 'em and if they cause
problems. And don't forget all the possible problems that arise from
production flaws (bad wafers etc.).

Anyway, concerning the original issue a bad PCB is probably rather the
issue. And SIL is as good a choice as Marvell or JMicron in most cases.

Regards

-Sven

On Sun, 2011-04-17 at 15:26 -0500, Stan Hoeppner wrote:

> The problem is almost never a design flaw with the main IC (whether
> SCSI, SATA, GPU, etc), but almost always the board implementation.  The
> big money is in the ICs, and they have high QC.  Board (PCB)
> manufacturing cost is often $0.50 USD/board or less.  If all $0.50 of
> that board making was QC, is that sufficient? (rhetorical)
> 



  reply	other threads:[~2011-04-17 21:18 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-14 10:31 Recommended pci-e 1x SATA cards Steven Haigh
2011-04-14 10:54 ` Roman Mamedov
2011-04-14 11:05   ` Tapani Tarvainen
2011-04-14 11:25     ` Roman Mamedov
2011-04-14 11:41       ` Tapani Tarvainen
2011-04-14 12:02         ` Roman Mamedov
2011-04-14 11:14   ` Steven Haigh
2011-04-14 19:37   ` Stan Hoeppner
2011-04-15  1:54     ` Brad Campbell
2011-04-15  5:03     ` Roman Mamedov
2011-04-14 12:53 ` Roman Mamedov
2011-04-14 13:16   ` Steven Haigh
2011-04-14 19:55     ` Stan Hoeppner
2011-04-14 23:50       ` Steven Haigh
2011-04-15  4:06         ` Stan Hoeppner
2011-04-15  4:35           ` Steven Haigh
2011-04-15  4:56             ` Stan Hoeppner
2011-04-15  4:58       ` Roman Mamedov
2011-04-15 21:31         ` Stan Hoeppner
2011-04-16  5:15           ` Roman Mamedov
2011-04-16  8:57             ` Brad Campbell
2011-04-16 20:40               ` Stan Hoeppner
2011-04-17  5:44                 ` Brad Campbell
2011-04-17 18:36                   ` Stan Hoeppner
2011-04-17 18:45                     ` Mikael Abrahamsson
2011-04-17 20:26                       ` Stan Hoeppner
2011-04-17 21:18                         ` Sven Eschenberg [this message]
2011-04-17 21:25                     ` Guy Watkins
2011-04-17 23:29                     ` Brad Campbell

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=1303075124.2009.28.camel@HansWurst \
    --to=sven@whgl.uni-frankfurt.de \
    --cc=linux-raid@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).