linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Greg Freemyer <greg.freemyer@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: [DOC] SATA status report updated
Date: Fri, 30 Jun 2006 02:51:27 +0900	[thread overview]
Message-ID: <44A4131F.8020904@gmail.com> (raw)
In-Reply-To: <87f94c370606290741v45e63336n30df5fdc6a5c2bac@mail.gmail.com>

Greg Freemyer wrote:
> On 6/27/06, Jeff Garzik <jeff@garzik.org> wrote:
>> Updated the SATA status report(s) found at
>>
>>         http://linux-ata.org/
>>
>> In particular, I created a matrix of drivers and features, to give
>> people an idea of fine-grained driver status:
>>
>>         http://linux-ata.org/driver-status.html#matrix
>>
>> As always, comments, questions, and additions are welcome.
>>
>>         Jeff
> Jeff / Tejun,
> 
> Great work.  If the feedback about reversion issues continues to be as
> minimal as it currently is it appears you appear to have rolled out a
> great enhancement with minimal errors introduced.  I expect to be
> using sata/e-sata much more extensively now that this new EH process
> is in place.
> 
> Any practical experience about which PCI controllers and/or enclosures
> would be best to get if I wanted to use e-Sata and the
> hotplug/warmplug logic?

I primarily work on sil controllers and ICH7R piix/ahci because I have 
access to the hardware and docs.  So, those tend to get new features 
first and get a lot of testing.

If you're planning on using Port Multiplier, sil3124/32 would be the 
best bet ATM.

-- 
tejun

  reply	other threads:[~2006-06-29 17:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-27  4:33 [DOC] SATA status report updated Jeff Garzik
2006-06-29 14:41 ` Greg Freemyer
2006-06-29 17:51   ` Tejun Heo [this message]
2006-06-29 14:46 ` Martin Hicks

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=44A4131F.8020904@gmail.com \
    --to=htejun@gmail.com \
    --cc=greg.freemyer@gmail.com \
    --cc=jeff@garzik.org \
    --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 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).