From: Jeff Garzik <jgarzik@pobox.com>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] SATA NCQ support
Date: Mon, 30 May 2005 21:21:31 -0400 [thread overview]
Message-ID: <429BBC1B.1060402@pobox.com> (raw)
In-Reply-To: <429BA937.2090802@shaw.ca>
Robert Hancock wrote:
> Jeff Garzik wrote:
>
>> Matthias Andree wrote:
>>
>>> OK, so this is for AHCI. What are the options for people whose
>>> mainboards aren't blessed with AHCI, but use for instance VIA or older
>>> Promise chips? Buy new hardware? Or wait until someone comes up with an
>>> implementation?
>>
>>
>>
>> As Jens mentioned, NCQ support requires both device and hardware have
>> explicit NCQ support. That eliminates most of Linux's supported SATA
>> controllers, none of which support NCQ.
>>
>> Don't have a heart attack, though, SATA is pretty fast even without NCQ.
>>
>
> NVIDIA nForce4 supports NCQ under Windows.. any word on whether docs may
> become available to allow this to be supported under Linux? You'd think
> NVIDIA would want to get that support in..
NVIDIA is the only company that hasn't been willing to give me any SATA
docs access, so who knows.
NVIDIA themselves wrote sata_nv, so presumably they'll support it
whenever people poke them enough.
Jeff
next prev parent reply other threads:[~2005-05-31 1:21 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48Hix-88s-7@gated-at.bofh.it>
[not found] ` <48N4N-4B5-25@gated-at.bofh.it>
[not found] ` <48Pzt-6Kb-5@gated-at.bofh.it>
2005-05-31 0:00 ` [PATCH] SATA NCQ support Robert Hancock
2005-05-31 1:21 ` Jeff Garzik [this message]
2005-05-27 7:03 Jens Axboe
2005-05-27 7:22 ` Jeff Garzik
2005-05-27 7:30 ` Jens Axboe
2005-05-27 7:37 ` Jeff Garzik
2005-05-27 7:47 ` Jens Axboe
2005-05-27 7:56 ` Jens Axboe
2005-05-27 8:24 ` Jeff Garzik
2005-05-27 8:27 ` Jeff Garzik
2005-05-27 8:28 ` Jeff Garzik
2005-05-27 8:35 ` Jens Axboe
2005-05-27 8:38 ` Jeff Garzik
2005-05-27 8:42 ` Jens Axboe
2005-05-27 23:47 ` Jeff Garzik
2005-05-27 13:18 ` Matthias Andree
2005-05-27 13:53 ` Jens Axboe
2005-05-27 14:46 ` Matthias Andree
2005-05-27 14:58 ` Jens Axboe
2005-05-29 13:16 ` Matthias Andree
2005-05-29 16:36 ` Jeff Garzik
2005-05-30 2:35 ` Eric D. Mudama
2005-05-30 3:41 ` Greg Stark
2005-05-30 4:04 ` Eric D. Mudama
2005-05-30 6:21 ` Greg Stark
2005-05-30 6:33 ` Jens Axboe
2005-05-30 12:16 ` Jens Axboe
2005-05-30 12:37 ` Jens Axboe
2005-05-30 14:51 ` Jens Axboe
2005-05-27 16:00 ` 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=429BBC1B.1060402@pobox.com \
--to=jgarzik@pobox.com \
--cc=hancockr@shaw.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox