From: Lion Vollnhals <webmaster@schiggl.de>
To: wrlk@riede.org
Cc: linux-kernel@vger.kernel.org, Allen Martin <AMartin@nvidia.com>
Subject: RE: NCQ support NVidia NForce4 (CK804) SATAII
Date: Sun, 14 Aug 2005 17:18:44 +0200 [thread overview]
Message-ID: <1124032724.9323.1.camel@localhost.localdomain> (raw)
In-Reply-To: <pan.2005.08.14.13.28.56.704434@riede.org>
Am Sonntag, den 14.08.2005, 09:29 -0400 schrieb Willem Riede:
> On Wed, 10 Aug 2005 20:54:35 +0000, Allen Martin wrote:
>
> > Likely the only way nForce4 NCQ support could be added under Linux would
> > be with a closed source binary driver, and no one really wants that,
> > especially for storage / boot volume. We decided it wasn't worth the
> > headache of a binary driver for this one feature. Future nForce
> > chipsets will have a redesigned SATA controller where we can be more
> > open about documenting it.
>
> That is disappointing. I was seriously considering a motherboard with your
> chipset because of its impressive specifications, but now I have to
> reconsider (I'm one of those folks that never bought an nVidia graphics
> board due to the lack of open full-function driver). I _hate_ not being
> able to use all features.
I agree.
I am considering buying an nForce4 board, too.
But i am discouraged by it's closed source nature.
Lion Vollnhals
next prev parent reply other threads:[~2005-08-14 15:19 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.psg95ip.1emqnop@ifi.uio.no>
2005-08-14 13:29 ` NCQ support NVidia NForce4 (CK804) SATAII Willem Riede
2005-08-14 15:18 ` Lion Vollnhals [this message]
2005-08-15 13:42 ` Stephen Frost
2005-08-18 14:23 ` Chris Wedgwood
[not found] <DBFABB80F7FD3143A911F9E6CFD477B004FAE3E7@hqemmail02.nvidia.com.suse.lists.linux.kernel>
[not found] ` <20050811070943.GB8025@vega.lgb.hu.suse.lists.linux.kernel>
[not found] ` <1123765523.32375.10.camel@mindpipe.suse.lists.linux.kernel>
[not found] ` <42FB6C27.1010408@gmail.com.suse.lists.linux.kernel>
[not found] ` <42FB88F8.7040807@pobox.com.suse.lists.linux.kernel>
2005-08-11 18:44 ` Andi Kleen
2005-08-10 20:53 Allen Martin
2005-08-10 21:31 ` Lennart Sorensen
2005-08-11 7:09 ` Gábor Lénárt
2005-08-11 13:05 ` Lee Revell
2005-08-11 15:17 ` Michael Thonke
2005-08-11 15:22 ` Lee Revell
2005-08-11 15:43 ` Michael Thonke
2005-08-11 16:18 ` Roger Heflin
2005-08-11 16:32 ` Michael Thonke
2005-08-12 19:02 ` Jan Engelhardt
2005-08-11 15:39 ` Diego Calleja
2005-08-12 6:17 ` Gábor Lénárt
2005-08-11 17:20 ` Jeff Garzik
2005-08-11 17:27 ` Lennart Sorensen
2005-08-11 17:44 ` Michael Thonke
2005-08-11 17:48 ` Lennart Sorensen
2005-08-11 19:29 ` Heikki Orsila
2005-08-11 17:38 ` Michael Thonke
2005-08-11 17:46 ` Jeff Garzik
2005-08-11 17:57 ` Michael Thonke
2005-08-11 18:32 ` Jeff Garzik
2005-08-11 18:55 ` Michael Thonke
2005-08-11 18:04 ` Lennart Sorensen
2005-08-11 18:17 ` Michael Thonke
2005-08-12 20:10 ` Andre Tomt
2005-08-11 15:09 ` Michael Thonke
2005-08-15 6:01 ` Christopher Chan
-- strict thread matches above, loose matches on Subject: below --
2005-08-10 18:59 Allen Martin
2005-08-10 18:11 Michael Thonke
2005-08-10 18:18 ` Jeff Garzik
2005-08-10 18:28 ` Michael Thonke
2005-08-10 18:52 ` Michael Thonke
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=1124032724.9323.1.camel@localhost.localdomain \
--to=webmaster@schiggl.de \
--cc=AMartin@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wrlk@riede.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