From: Erik Andersen <andersen@codepoet.org>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Jos Hulzink <josh@stack.nl>, jw schultz <jw@pegasys.ws>,
linux-kernel@vger.kernel.org
Subject: Re: DE and hot-swap disk caddies
Date: Wed, 27 Mar 2002 17:17:09 -0700 [thread overview]
Message-ID: <20020328001709.GA16582@codepoet.org> (raw)
In-Reply-To: <20020327235029.P78593-100000@snail.stack.nl> <Pine.LNX.4.10.10203271553520.6006-100000@master.linux-ide.org>
On Wed Mar 27, 2002 at 03:57:48PM -0800, Andre Hedrick wrote:
> > If you really want to build in IDE hot swap support, I demand it comes
> > with a warning: Enabling this option will probably destroy your harddisks
> > and your chipset. Feel free to continue, but don't blame us.
>
> FYI, there was almost a witch hunt when I went into T13 with a SCA4ATA
> proposal. You understand the issue and I am glad it was you and not me to
> have to bang this drum. Thanks.
Ok. How about my laptop? I have an ATAPI zip drive I can plug
in instead of a second battery. It is the only device on the
second IDE bus (hdc). In windows there is a little hotplug
utility thing one runs before unplugging the zip drive. In Linux
I currently have to reboot if I want the ide-floppy driver to see
the device... I'm willing to bet that Dell has done mysterious
stuff to make the electrical part work. It would sure be nice if
I could ask the ide driver to kindly re-scan for /dev/hdc now.
Is whatever windows is doing when I hotplug my zip drive somehow
unsafe, such that supporting the same functionality on Linux is
somehow a Bad Thing(tm)?
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
next prev parent reply other threads:[~2002-03-28 0:17 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-25 9:32 IDE and hot-swap disk caddies John Summerfield
2002-03-25 15:56 ` Alan Cox
2002-03-25 19:34 ` Bill Davidsen
2002-03-25 19:55 ` Alan Cox
2002-03-25 20:26 ` Wakko Warner
2002-03-25 21:20 ` Andre Hedrick
2002-03-25 22:32 ` Wakko Warner
2002-03-26 0:11 ` Thunder from the hill
2002-03-26 18:52 ` Pavel Machek
2002-03-27 22:38 ` Alan Cox
2002-03-27 22:29 ` Pavel Machek
2002-03-27 22:47 ` Pedro M. Rodrigues
2002-03-27 23:21 ` Jos Hulzink
2002-03-28 11:37 ` Jos Hulzink
2002-03-27 22:51 ` Alan Cox
2002-03-28 0:01 ` Itai Nahshon
2002-03-28 0:11 ` Andre Hedrick
2002-03-27 23:53 ` Vojtech Pavlik
2002-03-25 23:16 ` John Summerfield
2002-03-26 3:32 ` Mark Lord
2002-03-26 5:28 ` Jeremy Jackson
2002-03-26 8:21 ` DE " jw schultz
2002-03-26 19:01 ` Pavel Machek
2002-03-27 22:34 ` jw schultz
2002-03-27 23:17 ` Jos Hulzink
2002-03-27 23:57 ` Andre Hedrick
2002-03-28 0:17 ` Erik Andersen [this message]
2002-03-28 0:23 ` Andre Hedrick
2002-03-28 0:31 ` Benjamin LaHaise
2002-03-28 0:40 ` Andre Hedrick
2002-03-28 2:02 ` IDE " Jeremy Jackson
2002-03-28 9:33 ` Alan Cox
2002-03-28 9:28 ` Simon Richter
2002-03-28 16:25 ` Jeremy Jackson
2002-03-28 9:33 ` DE " Jos Hulzink
2002-03-28 0:37 ` Alan Cox
2002-03-28 0:27 ` Andre Hedrick
2002-03-28 4:24 ` Chuck Campbell
2002-03-28 4:32 ` Andre Hedrick
2002-03-28 8:00 ` Martin Dalecki
2002-03-28 8:21 ` Andre Hedrick
2002-03-28 9:01 ` Martin Dalecki
2002-03-28 9:39 ` Alan Cox
2002-03-28 9:50 ` Offtopic: " Jos Hulzink
2002-03-28 9:53 ` Martin Dalecki
2002-03-28 18:31 ` Herman Oosthuysen
2002-03-28 9:29 ` Jos Hulzink
2002-03-26 22:53 ` IDE " John Summerfield
2002-03-28 16:46 ` Bill Davidsen
2002-03-28 18:10 ` Mark Lord
2002-03-28 20:59 ` John Summerfield
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=20020328001709.GA16582@codepoet.org \
--to=andersen@codepoet.org \
--cc=andre@linux-ide.org \
--cc=josh@stack.nl \
--cc=jw@pegasys.ws \
--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