From: Jeff Garzik <jgarzik@pobox.com>
To: Matthias Andree <matthias.andree@gmx.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Promise SATA driver GPL'd
Date: Wed, 27 Aug 2003 07:51:53 -0400 [thread overview]
Message-ID: <3F4C9B59.20504@pobox.com> (raw)
In-Reply-To: <20030827090020.GC9054@merlin.emma.line.org>
Matthias Andree wrote:
> On Tue, 26 Aug 2003, Jeff Garzik wrote:
>
>
>>For the future, I'm currently whipping the libata internals into shape
>>so that Promise may be supported. Promise hardware supports native
>>command queueing, a lot like many SCSI adapters.
>
>
> Is that true even for the older stuff such as a PDC20265?
PATA stuff will continue to be supported via drivers/ide, I'm only
shooting for the newer SATA stuff.
> It appears that FreeBSD 4-STABLE blacklists some older (before-TX2)
> Promise chips because they apparently lock up when used with tagged
> command queueing. I haven't yet looked at the ATAng driver merged into
> FreeBSD 5-CURRENT.
ATA tagged command queueing is a bunch of crap. :) I'm not sure
whether I want to implement it or not.
I was referring to _native_ command queueing. ATA TCQ is something
different. ATA TCQ does not allow multiple outstanding scatter/gather
tables to be sent to the host controller. Native command queuing does.
Jeff
next prev parent reply other threads:[~2003-08-27 11:52 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-22 18:45 Promise SATA driver GPL'd Erik Andersen
2003-07-22 18:54 ` Jeff Garzik
2003-07-22 19:07 ` Erik Andersen
2003-07-22 19:39 ` Samuel Flory
2003-07-22 20:56 ` Jeff Garzik
2003-07-22 21:39 ` Erik Andersen
2003-07-22 23:25 ` Jeff Garzik
2003-08-27 3:01 ` Nick Urbanik
2003-08-27 3:14 ` Jeff Garzik
2003-08-27 9:00 ` Matthias Andree
2003-08-27 11:51 ` Jeff Garzik [this message]
2003-07-22 20:57 ` Jeff Garzik
2003-07-23 13:20 ` Mark Watts
2003-07-23 1:59 ` Andre Hedrick
2003-07-23 2:38 ` Shawn
2003-07-23 10:32 ` Alan Cox
2003-07-23 18:58 ` Andre Hedrick
2003-07-24 11:22 ` Matthias Andree
2003-08-13 13:34 ` Vojtech Pavlik
2003-08-13 14:24 ` Jeff Garzik
2003-08-15 10:17 ` Andre Hedrick
2003-07-25 3:44 ` Milan Roubal
2003-07-23 5:12 Adam J. Richter
2003-07-23 5:28 ` Andre Hedrick
2003-07-23 9:08 ` Adrian Bunk
2003-07-23 10:12 ` Matthias Andree
2003-07-23 10:21 ` Wichert Akkerman
2003-07-23 11:47 ` Alan Cox
2003-07-23 11:54 ` Wichert Akkerman
2003-07-23 10:37 ` Adrian Bunk
2003-07-23 10:29 ` Alan Cox
2003-07-23 10:51 ` Adrian Bunk
2003-07-23 11:43 ` Alan Cox
2003-07-23 12:17 ` Adrian Bunk
2003-07-23 12:32 ` Martin Diehl
2003-07-23 12:57 ` Alan Cox
2003-07-23 19:08 ` Andre Hedrick
2003-07-23 19:19 ` Alan Cox
2003-07-23 19:33 ` Andre Hedrick
2003-07-23 19:46 ` Andre Hedrick
2003-07-23 20:59 ` Roman Zippel
2003-07-23 22:22 ` Andre Hedrick
2003-07-23 22:40 ` Roman Zippel
2003-07-23 22:35 ` Andre Hedrick
2003-07-23 23:02 ` Roman Zippel
2003-07-23 23:08 ` Andre Hedrick
2003-07-23 23:33 ` Roman Zippel
2003-07-23 23:45 ` Andre Hedrick
2003-07-24 0:14 ` dacin
2003-07-24 0:23 ` Andre Hedrick
2003-07-24 0:21 ` David Schwartz
2003-07-24 0:21 ` Andre Hedrick
2003-07-24 13:23 ` Jesse Pollard
2003-07-24 14:01 ` Richard B. Johnson
2003-07-24 18:37 ` David Schwartz
2003-07-23 22:32 ` Andre Hedrick
2003-07-23 22:46 ` Larry McVoy
2003-07-23 23:13 ` Roman Zippel
2003-07-23 10:40 ` Adam Sampson
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=3F4C9B59.20504@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.andree@gmx.de \
/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;
as well as URLs for NNTP newsgroup(s).