From: Jeff Garzik <jeff@garzik.org>
To: peer chen <peerchen@gmail.com>, Kuan Luo <kluo@nvidia.com>,
Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-ide <linux-ide@vger.kernel.org>,
akpm <akpm@linux-foundation.org>
Subject: Re: [PATCH] sata_nv,ahci: add the ahci legacy mode support to sata_nv
Date: Sat, 10 Nov 2007 00:00:24 -0500 [thread overview]
Message-ID: <47353AE8.5050900@garzik.org> (raw)
In-Reply-To: <47352DD8.6040607@garzik.org>
Jeff Garzik wrote:
> The proposed sata_nv patch does the opposite -- guarantees we must
> support the continually problematic legacy IDE interface ad infinitum.
> Such patches are OK for the test lab, but in this specific case users
> /suffer/ when not running AHCI mode.
Just to reinforce...
sata_nv support and bug fixes are primarily done right now through the
valiant efforts of Robert Hancock (with assists from Alan, Tejun, and
others).
Robert's job is difficult, because he has no hardware documentation[1],
and NVIDIA does not seem to be helping out much with driver bug reports
on the lists or in bugzillas.
As far as I know, I am the only one in the universe outside of NVIDIA
with any SATA docs at all, and those docs _only_ cover ADMA registers
and DMA structures, no PCI config info, no errata, nothing on SWNCQ or
legacy IDE (well, half a page).
NVIDIA has indeed become more engaged in sata_nv in recent times, and
that's a positive sign. You, Kuon and Ayaz have all been noticeably
more responsive in email. Thanks. Users have definitely benefited,
particularly from your help addressing a couple SWNCQ issues.
But at this point in time, being asked to choose between sata_nv and
ahci is no choice at all. One has public documentation, wide industry
support and little-or-no bugs. The other has several open issues, no
documentation, and support obstacles.
Jeff
[1] Robert, please correct me if I'm wrong...
next prev parent reply other threads:[~2007-11-10 5:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 5:23 [PATCH] sata_nv,ahci: add the ahci legacy mode support to sata_nv Peer Chen
2007-09-25 7:08 ` Jeff Garzik
2007-09-25 7:52 ` Peer Chen
2007-09-25 8:13 ` Jeff Garzik
2007-09-25 9:08 ` Peer Chen
2007-10-12 21:17 ` Jeff Garzik
2007-10-16 8:08 ` peer chen
2007-10-19 2:56 ` Jeff Garzik
2007-10-19 6:58 ` peer chen
2007-10-19 7:25 ` Jeff Garzik
2007-10-22 1:55 ` peer chen
2007-11-10 4:04 ` Jeff Garzik
2007-11-10 5:00 ` Jeff Garzik [this message]
2007-11-10 19:00 ` Robert Hancock
2007-12-11 12:04 ` [PATCH] sata_nv,adma: fix error when rmmod sata_nv Kuan Luo
2007-12-12 8:18 ` Tejun Heo
2007-12-13 3:10 ` Kuan Luo
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=47353AE8.5050900@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=hancockr@shaw.ca \
--cc=kluo@nvidia.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peerchen@gmail.com \
/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