linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	pchen@nvidia.com, kernel-bugzilla.20.drkshadow@spamgourmet.com
Subject: Re: [PATCH #upstream-fixes 3/3] ahci: implement AHCI_HFLAG_NO_FPDMA_AA and update NV quirks
Date: Fri, 12 Mar 2010 10:16:59 +0900	[thread overview]
Message-ID: <4B99960B.6060902@kernel.org> (raw)
In-Reply-To: <4B9985E9.5010909@gmail.com>

Hello,

On 03/12/2010 09:08 AM, Robert Hancock wrote:
> On 03/10/2010 08:40 PM, Tejun Heo wrote:
>> It turns out different generations of MCPs have differing quirks.
>>
>> * MCP 65-73 : FPDMA AA broken, lies about PMP support, forgets to
>> report NCQ
>> * MCP 77-79 : FPDMA AA broken, lies about PMP support
>> * MCP 89    : FPDMA AA broken
>>
>> Instead of turngin off FPDMA AA on all NVIDIAs, implement
>> HFLAG_NO_FPDMA_AA, define additional board IDs and apply necessary
>> quirks.
>>
>> This fixes bko#15481 and the list of quirks is verified by Peer Chen.
>>
>>    http://bugzilla.kernel.org/show_bug.cgi?id=15481
>>
>> Signed-off-by: Tejun Heo<tj@kernel.org>
>> Cc: Peer Chen<pchen@nvidia.com>
> 
> Is the FPDMA AA problem going to be fixed in whatever follows MCP89?
> This change is only safe if it will be, since a new chipset will fall
> into the generic case and it'll get turned back on.

Yeap, it would be great if NVIDIA fixes it but that said blacklisting
by default usually isn't a very good idea because it often falls
through the crack and after a while not many people remember what
happened when.  If NVIDIA doesn't fix the next revision, we'll know
soon enough.

Thanks.

-- 
tejun

  reply	other threads:[~2010-03-12  1:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-11  2:37 [PATCH #upstream-fixes 1/3] ahci: add missing nv IDs Tejun Heo
2010-03-11  2:39 ` [PATCH #upstream-fixes 2/3] ahci: clean up board IDs Tejun Heo
2010-03-11  2:40   ` [PATCH #upstream-fixes 3/3] ahci: implement AHCI_HFLAG_NO_FPDMA_AA and update NV quirks Tejun Heo
2010-03-12  0:08     ` Robert Hancock
2010-03-12  1:16       ` Tejun Heo [this message]
2010-03-17 17:44   ` [PATCH #upstream-fixes 2/3] ahci: clean up board IDs Jeff Garzik
2010-03-17 22:58     ` Tejun Heo
2010-03-17 23:04       ` Jeff Garzik
2010-03-18  0:02         ` Tejun Heo
2010-03-17 17:47 ` [PATCH #upstream-fixes 1/3] ahci: add missing nv IDs Jeff Garzik

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=4B99960B.6060902@kernel.org \
    --to=tj@kernel.org \
    --cc=hancockrwd@gmail.com \
    --cc=jeff@garzik.org \
    --cc=kernel-bugzilla.20.drkshadow@spamgourmet.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=pchen@nvidia.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;
as well as URLs for NNTP newsgroup(s).