From: Jeff Garzik <jgarzik@pobox.com>
To: Justin Cormack <justin@street-vision.com>
Cc: Andre Tomt <lkml@tomt.net>,
Kernel mailing list <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Serial ATA (SATA) for Linux status report
Date: Thu, 04 Dec 2003 09:54:03 -0500 [thread overview]
Message-ID: <3FCF4A8B.6030701@pobox.com> (raw)
In-Reply-To: <1070545088.11956.43.camel@lotte.street-vision.com>
Justin Cormack wrote:
> On Wed, 2003-12-03 at 23:36, Jeff Garzik wrote:
>
>>Andre Tomt wrote:
>>
>>>On Wed, 2003-12-03 at 21:44, Jeff Garzik wrote:
>>>
>>>
>>>>Intel ICH5
>>>>----------
>>>>Summary: No TCQ. Looks like a PATA controller, but with a few added,
>>>>non-standard SATA port controls.
>>
>>>One question - with "including hotplug", does that mean some set hotplug
>>>standard? Reason I'm asking is, we have a few servers from SuperMicro,
>>>with a ICH5R S-ATA controller that claims it's supporting hotplug, but
>>>hotplug is not in your ICH5-summary.
>>
>>Alas, there is no hotplug support in the ICH5 or ICH5-R SATA hardware.
>>
>>One could argue there is "coldplug" support in that hardware -- disable
>>the entire interface, including any active devices, then re-enable and
>>re-scan -- but it's a bit of a hack. If there's enough demand, I could
>>write some code for that. It would involve something like
>>
>> # /sbin/sata off
>> { plug in or remove a device }
>> # /sbin/sata on
>>
>>You really, really, really don't want to actually unplug a SATA drive
>>while it's active, on ICH5 hardware.
>
>
> How does it work on other hardware?
Just yank the cord :)
Jeff
next prev parent reply other threads:[~2003-12-04 14:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 20:44 Serial ATA (SATA) for Linux status report Jeff Garzik
2003-12-03 23:27 ` Andre Tomt
2003-12-03 23:36 ` Jeff Garzik
2003-12-03 23:49 ` Othmar Pasteka
2003-12-03 23:51 ` Jeff Garzik
2003-12-04 0:59 ` Samuel Flory
2003-12-04 1:02 ` Andre Tomt
2003-12-04 13:38 ` Justin Cormack
2003-12-04 14:54 ` Jeff Garzik [this message]
2003-12-04 8:17 ` Arnaud Launay
2003-12-04 15:01 ` Jeff Garzik
[not found] ` <200312051842.26599.marchand@kde.org>
[not found] ` <3FD0C4B0.8020106@pobox.com>
[not found] ` <200312051907.13727.marchand@kde.org>
2003-12-09 18:22 ` [PATCH] Silicon image 3114 SATA link (really basic support) Aron Rubin
2003-12-09 18:54 ` Mickael Marchand
2003-12-09 20:14 ` Bartlomiej Zolnierkiewicz
2003-12-12 0:07 ` Mickael Marchand
2003-12-09 19:59 ` Serial ATA (SATA) for Linux status report J. Ryan Earl
2004-01-14 22:18 ` Greg Stark
2004-01-14 22:56 ` Erik Andersen
2004-01-14 23:31 ` James Courtier-Dutton
2004-01-15 0:41 ` Jeff Garzik
2004-01-15 2:38 ` Erik Andersen
2004-01-18 12:34 ` Martin Schlemmer
2004-01-14 23:12 ` Erik Steffl
2004-01-18 13:32 ` Witold Krecicki
2004-01-18 18:00 ` Jeff Garzik
2004-01-18 20:33 ` Craig Bradney
-- strict thread matches above, loose matches on Subject: below --
2004-08-24 19:49 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=3FCF4A8B.6030701@pobox.com \
--to=jgarzik@pobox.com \
--cc=justin@street-vision.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lkml@tomt.net \
/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).