From: otto Meier <gf435@gmx.net>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: More Promise chipset specs opened
Date: Sun, 05 Nov 2006 09:58:17 +0100 [thread overview]
Message-ID: <454DA7A9.7000608@gmx.net> (raw)
In-Reply-To: <454C92D2.8060809@garzik.org>
Jeff Garzik schrieb:
> otto Meier wrote:
>> In which controller classes does it belong?
>> Promise claims it should have NCQ how to enable ?
>
> If it claims NCQ and 3.0Gbps support, I would guess 205xx
>
> Jeff
>
Does this mean, changing :
{ PCI_VDEVICE(PROMISE, 0x3d17), board_20319 },
to
{ PCI_VDEVICE(PROMISE, 0x3d17), board_2057X },
in sata_promise.c would do the trick to activate NCQ of this board?
Does this hurt?
Do I need to do something else to get NCQ working?
Otto
next prev parent reply other threads:[~2006-11-05 8:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-04 10:11 More Promise chipset specs opened otto Meier
2006-11-04 13:17 ` Jeff Garzik
2006-11-05 8:58 ` otto Meier [this message]
2006-11-05 9:41 ` Jeff Garzik
2006-11-05 10:11 ` otto Meier
-- strict thread matches above, loose matches on Subject: below --
2006-11-02 5:12 Promise 20319 " Jeff Garzik
2006-11-02 5:46 ` More Promise " 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=454DA7A9.7000608@gmx.net \
--to=gf435@gmx.net \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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.