From: Tejun Heo <htejun@gmail.com>
To: yahoo-groups@omega71.com
Cc: linux-ide@vger.kernel.org
Subject: Re: AHCI NCQ on ESB2 (8086:2681)
Date: Mon, 01 Jan 2007 12:20:38 +0900 [thread overview]
Message-ID: <45987E06.1070101@gmail.com> (raw)
In-Reply-To: <4597B34C.1090606@omega71.com>
Bryan Boatright wrote:
>
> I hope this is an appropriate place to ask this question. Googling for
> answers turned up nothing.
>
> I am using kernel 2.6.19.1 and am trying to get NCQ support working. My
> Intel chipset (ESB2, see details below) should support NCQ, but it is
> not returning the NCQ capabilities bit in the HBA Capabilities
> register. Here's the relevant dmesg output:
Please test the latest Linus git-tree. ahci used to clear CAP while
resetting controller expecting it to set supported feature bits again.
Apparently some controllers don't do it resulting in disabled NCQ.
This was fixed recently by the following commit.
Commit: 551c012d7eea3dc5ec063c7ff9c718d39e77634f
Author: Tejun Heo <htejun@gmail.com> 2006-12-12 20:17:32
Committer: Jeff Garzik <jeff@garzik.org> 2006-12-17 00:13:29
Branches: upstream-fixes, upstream, quilt-init
Follows: v2.6.19
Precedes:
[PATCH] ahci: do not mangle saved HOST_CAP while resetting controller
Do not mangle with HOST_CAP while resetting controller. The code is
there for a historical reason. The mangling breaks controller feature
detection and 0 PORTS_IMPL workaround code.
This problem was spotted by Manoj Kasichainula.
Signed-off-by: Tejun Heo <htejun@gmail.com>
Cc: Manoj Kasichainula <manoj@io.com>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
Happy new year.
--
tejun
next prev parent reply other threads:[~2007-01-01 10:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-31 12:55 AHCI NCQ on ESB2 (8086:2681) Bryan Boatright
2006-12-31 19:14 ` Dave Maurer
2007-01-01 3:20 ` Tejun Heo [this message]
2007-01-01 14:32 ` AHCI NCQ on ESB2 (8086:2681) (RESOLVED) Bryan Boatright
2007-01-01 14:35 ` AHCI NCQ on ESB2 (8086:2681) Bryan Boatright
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=45987E06.1070101@gmail.com \
--to=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=yahoo-groups@omega71.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).