From: Bastiaan Jacques <b.jacques@planet.nl>
To: Tejun Heo <htejun@gmail.com>
Cc: boac@wanadoo.nl, linux-ide@vger.kernel.org
Subject: Re: Seagate SATA 3GB/s drive connected to via vt8251 using ahci module
Date: Tue, 20 Jun 2006 21:31:12 +0200 [thread overview]
Message-ID: <200606202131.12654.b.jacques@planet.nl> (raw)
In-Reply-To: <4498163C.90601@gmail.com>
On Tuesday 20 June 2006 17:37, Tejun Heo wrote:
> [CC'ing Bastiaan Jacques. Hi!]
Hey!
> Do you happen to have a different drive which can do NCQ?
> Preferably, one from another vendor?
I've just tried it with a Maxtor drive supporting NCQ, and it didn't
work.
> AFAICS, the ahci driver is
> doing NCQ as the AHCI spec specifies and all ICH controllers seem to
> be quite happy with it. I wanna know whether the problem is from the
> specific combination of the controller and the drive or the via
> controller needs a different programming sequence for NCQ in general.
It would seem the problem is in the VIA controller. Surprise, surprise.
> Bastiaan, do you know whether we need to do things differently to use
> NCQ on vt8251?
Apparently we have a hardware or firmware bug to work around, but I have
no idea what we should be doing differently.
--
Bastiaan
next prev parent reply other threads:[~2006-06-20 19:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-08 17:30 Seagate SATA 3GB/s drive connected to via vt8251 using ahci module Aalderd Bouwman
2006-06-09 5:44 ` Tejun Heo
2006-06-12 10:42 ` Aalderd Bouwman
2006-06-12 10:51 ` Tejun Heo
2006-06-12 11:24 ` Aalderd Bouwman
2006-06-18 2:56 ` Tejun Heo
2006-06-19 17:10 ` Aalderd Bouwman
2006-06-19 17:18 ` Tejun Heo
[not found] ` <1150745738.4302.1.camel@anja>
[not found] ` <20060620023312.GA1250@htj.dyndns.org>
2006-06-20 15:21 ` Aalderd Bouwman
2006-06-20 15:37 ` Tejun Heo
2006-06-20 19:31 ` Bastiaan Jacques [this message]
2006-06-21 7:25 ` Aalderd Bouwman
2006-06-21 14:12 ` [PATCH] ahci: disable NCQ support on vt8251 Tejun Heo
2006-06-23 3:22 ` 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=200606202131.12654.b.jacques@planet.nl \
--to=b.jacques@planet.nl \
--cc=boac@wanadoo.nl \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.