From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <htejun@gmail.com>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
"Hemmann, Volker Armin" <volker.armin.hemmann@tu-clausthal.de>,
Peer Chen <pchen@nvidia.com>
Subject: Re: [PATCH #upstream-fixes] ahci: workarounds for mcp65
Date: Fri, 13 Jun 2008 02:43:10 -0400 [thread overview]
Message-ID: <485216FE.3010404@garzik.org> (raw)
In-Reply-To: <484D4880.2050103@gmail.com>
Tejun Heo wrote:
> MCP65 ahci can do NCQ but doesn't set the CAP bit and rev A0 and A1
> can't do MSI but have MSI capability. Implement AHCI_HFLAG_YES_NCQ
> and apply appropriate workarounds.
>
> Signed-off-by: Tejun Heo <htejun@gmail.com>
> Cc: Peer Chen <pchen@nvidia.com>
> ---
> drivers/ata/ahci.c | 40 +++++++++++++++++++++++++++++++---------
> 1 file changed, 31 insertions(+), 9 deletions(-)
applied
prev parent reply other threads:[~2008-06-13 6:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-09 15:13 [PATCH #upstream-fixes] ahci: workarounds for mcp65 Tejun Heo
2008-06-11 21:27 ` Hemmann, Volker Armin
2008-06-13 6:43 ` Jeff Garzik [this message]
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=485216FE.3010404@garzik.org \
--to=jeff@garzik.org \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=pchen@nvidia.com \
--cc=volker.armin.hemmann@tu-clausthal.de \
/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).