All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Besard <tim.besard@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org
Subject: NCQ on Promise SATA300 TX4
Date: Wed, 17 Sep 2008 23:42:08 +0200	[thread overview]
Message-ID: <1221687728.12558.12.camel@tim-desktop> (raw)

Hi,

I recently bough a Promise SATA300 TX4 controller, which I am using in
combination with an NCQ-capable harddrive. As the controller supports
NCQ [1], and the libata webpages seems to indicate [2] that the
sata_promise driver does as well, I am currently trying to enable NCQ
(kernel 2.6.27).

Without any luck however, my dmesg log indicates the following:
[    4.244047] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    4.253636] ata1.00: ATA-7: ST3500320AS, SD04, max UDMA/133
[    4.253639] ata1.00: 976773168 sectors, multi 0: LBA48 NCQ (depth
0/32)
[    4.268850] ata1.00: configured for UDMA/133

And the NCQ queue depth flag seems read-only:
tim@tim-desktop:~$ sudo echo 31 > /sys/block/sdb/device/queue_depth
bash: /sys/block/sdb/device/queue_depth: Permission denied

The read-only nature of the queue_depth field seems to indicate that the
SATA module doesn't have NCQ support, but this contradicts with what I
read on the libata page.

Could you shed some light on this issue? And if the driver doesn't
support NCQ for this card, is there another way to accomplish this
(without having to buy a new controller)?

References:
1:
http://www.promise.com/product/product_detail_eng.asp?segment=Non-RAID%
20HBAs&product_id=139
2: http://linux-ata.org/driver-status.html#tx2

Thanks in advance,
Tim


             reply	other threads:[~2008-09-17 21:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-17 21:42 Tim Besard [this message]
2008-09-17 22:25 ` NCQ on Promise SATA300 TX4 Alexander Beregalov
2008-09-18  7:45 ` Mikael Pettersson

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=1221687728.12558.12.camel@tim-desktop \
    --to=tim.besard@gmail.com \
    --cc=jgarzik@pobox.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.