From: Jeremy Jackson <jerj@coplanar.net>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Ron House <house@usq.edu.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: hdparm and removable IDE?
Date: 31 Mar 2003 15:48:54 -0500 [thread overview]
Message-ID: <1049143734.1258.46.camel@contact.skynet.coplanar.net> (raw)
In-Reply-To: <Pine.LNX.3.96.1030331140112.32749A-100000@gatekeeper.tmr.com>
On Mon, 2003-03-31 at 14:14, Bill Davidsen wrote:
> > IDE bus to disconnect/*reconnect*?) But hot swap will always affect both
> > cables.
>
> Boy I hope that's a typo... I hope you meant both devices on a cable and
> not really both cables on a controller.
Yep, sorry. The IDE controller must tri-state off an entire cable...
both devices. I guess you could have 2 devices, and swap one but leave
the other, you just have to halt all IO durring the swap, perhaps reset
both devices when the cable is switched back on.
Interesting to note, Intel's PIIX (forget what version) had a feature
that would split the primary cable (from the OS point of view - think
dos here) so the master was on the primary cable, and the slave was on
the secondary cable. each device (ie swap bay in a laptop) could be
tristated separately. of course you loose the secondary channel.
--
Jeremy Jackson <jerj@coplanar.net>
next prev parent reply other threads:[~2003-03-31 20:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-26 4:41 Ron House
2003-03-26 14:33 ` Alan Cox
2003-03-26 18:11 ` Bill Davidsen
2003-03-28 3:21 ` Ron House
2003-03-28 14:04 ` Jeremy Jackson
2003-03-28 16:55 ` Alan Cox
2003-03-29 11:34 ` Andre Hedrick
2003-03-31 4:41 ` Ron House
2003-03-31 9:30 ` John Bradford
2003-03-31 11:08 ` Alan Cox
2003-03-31 11:21 ` John Bradford
2003-03-31 11:43 ` Alan Cox
2003-03-31 19:14 ` Bill Davidsen
2003-03-31 20:48 ` Jeremy Jackson [this message]
2003-03-28 3:03 ` Ron House
2003-03-28 17:17 ` Alan Cox
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=1049143734.1258.46.camel@contact.skynet.coplanar.net \
--to=jerj@coplanar.net \
--cc=davidsen@tmr.com \
--cc=house@usq.edu.au \
--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
all inboxes | Powered by JetHome®