All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: monz@danbbs.dk
Cc: Linux IDE Mailing List <linux-ide@vger.kernel.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: SATA status report updated
Date: Fri, 12 Aug 2005 17:33:17 -0400	[thread overview]
Message-ID: <42FD159D.7080107@pobox.com> (raw)
In-Reply-To: <42FCF5D3.1080409@danbbs.dk>

Mogens Valentin wrote:
> Jeff Garzik wrote:
> 
>>
>> Things in SATA-land have been moving along recently, so I updated the 
>> software status report:
>>
>>     http://linux.yyz.us/sata/software-status.html
> 
> 
>  >> Queueing support, NCQ:
>  >> #3 will be supported by libata, for all hardware and devices that
>  >> support NCQ.
> 
> I guess this means libata support for HW-based NCQ.
> It also could mean software/driver implemented NCQ, which could work on 
> chipsets not supporting HW-NCQ in unison with a disk having NCQ?

NCQ by definition -requires- support in the controller chip.


>> Although I have not updated it in several weeks, folks may wish to 
>> refer to the hardware status report as well:
>>
>>     http://linux.yyz.us/sata/sata-status.html
> 
> 
> How well does libata work with the newest ULi chipsets?
> If not well, is there a possible timeframe?

No idea.  I don't see many bug reports, so I suppose its OK.

	Jeff



  reply	other threads:[~2005-08-12 21:33 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-12  5:09 SATA status report updated Jeff Garzik
2005-08-12  5:40 ` Rob van Nieuwkerk
2005-08-12  5:45   ` Jeff Garzik
2005-08-12 18:07     ` David Greaves
2005-08-12 10:44 ` Matthew Garrett
2005-08-12 21:30   ` Jeff Garzik
2005-08-13  8:45     ` Erik Slagter
2005-08-13  8:45     ` Erik Slagter
2005-08-12 14:18 ` Luben Tuikov
2005-08-12 14:18 ` Luben Tuikov
2005-08-12 14:18 ` Luben Tuikov
2005-08-12 14:46 ` Luben Tuikov
2005-08-12 19:17 ` Mogens Valentin
2005-08-12 19:17 ` Mogens Valentin
2005-08-12 19:17 ` Mogens Valentin
2005-08-12 21:33   ` Jeff Garzik [this message]
2005-08-19  8:09 ` Simon Oosthoek
2005-08-21 17:11 ` Mogens Valentin
2005-08-21 18:05   ` Jeff Garzik
2005-08-21 22:00     ` Mogens Valentin
  -- strict thread matches above, loose matches on Subject: below --
2005-08-12 10:24 Daniel J Blueman
2005-08-12 21:30 ` Jeff Garzik
     [not found] <4AA7B-4jm-5@gated-at.bofh.it>
     [not found] ` <4DagM-7c8-43@gated-at.bofh.it>
2005-08-19  9:14   ` Rainer Koenig
2005-08-19 18:34     ` Jeff Garzik
2005-08-19 23:01       ` Simon Oosthoek
2005-08-20  0:02         ` Jeff Garzik
     [not found] <4DbcF-8ux-3@gated-at.bofh.it>
     [not found] ` <4DbcG-8ux-5@gated-at.bofh.it>
     [not found]   ` <4DbcF-8ux-1@gated-at.bofh.it>
     [not found]     ` <4DjWG-4ea-19@gated-at.bofh.it>
     [not found]       ` <4Do9X-1IZ-5@gated-at.bofh.it>
     [not found]         ` <4Dp62-304-15@gated-at.bofh.it>
2005-08-20 15:36           ` Rainer Koenig
2005-08-22  8:07             ` Simon Oosthoek
2005-08-22 18:07               ` Rainer Koenig
2006-05-15 15:20 Jeff Garzik
2006-05-15 17:07 ` Sven-Haegar Koch
2006-05-15 18:17   ` 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=42FD159D.7080107@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=monz@danbbs.dk \
    /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.