public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Xavier Spriet <xavier@eliquid.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Sil SATA Controlers
Date: Thu, 25 Sep 2003 10:43:30 -0400	[thread overview]
Message-ID: <1064501009.14931.42.camel@shadow.eliquid.com> (raw)


-- 
Sincerely,

Xavier Spriet <xavier@eliquid.com>
IT Director
eliquidMEDIA International Inc.
Phone: (1-519)-973-1930
1-800  : (1-800)-561-7525
Fax     : (1-519)-253-0337

>From what I've gathered reading the archives, the Sillicon Image SATA
controlers that appear to ship with many newer boards is a rather
problematic controller and apparently, the latest drivers for these
controllers do not seem to provide the performance and stability
expected.

>From the information I was able to find on this list, the development of
a proper solution is a difficult challenge because of the NDA
implemented by Sil.

As I have not been able to find out the terms of this NDA, I'd like to
know if this NDA would actually prevent kernel developers to come up
with a proper driver.

If this is the case as it appears to be, would it be a good idea to both
complain to Sil for the terms of this NDA and ask them to be a little
more reasonable, and let my board's manufacturer (ASUS) know about the
issue and hope they will put pressure on Sil to change the terms of this
NDA or come up with an open-source driver or documentation, etc..?

Currently, I've been able to restore the high performance with this
driver in my scenario by forcing rqsize to remain at 128 instead of
switching to 15, and setting non-used interfaces back to 15.
Unfortunately, this seems to have brought back some occasional hangs of
the system.

Thanks,

Xavier.



                 reply	other threads:[~2003-09-25 14:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1064501009.14931.42.camel@shadow.eliquid.com \
    --to=xavier@eliquid.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