From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Dave Lawrence <dgl@integrinautics.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: compact flash IDE hot-swap summary please
Date: 23 Jul 2003 21:13:51 +0100 [thread overview]
Message-ID: <1058991230.5515.126.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <20030723204954.A439@flint.arm.linux.org.uk>
On Mer, 2003-07-23 at 20:49, Russell King wrote:
> > Drive level hotswap is supported only in the "I unmounted it all
> > properly first" case and providing your system has the required bus
> > isolation. Typically its also only allowed in IDE if you have a
> > single disk on the channel. With dual device you tend to have nasty
> > accidents pulling something out while the other device is "live"
>
> Any ideas if this is going to be fixed for 2.6? I think this is a show
> stopper, certainly for embedded devices - a fair number of people do use
> CF cards in their embedded solutions, and some of us hotplug CF cards to
> grab images off our digital cameras.
Everyone I know is using the PCMCIA interface stuff for that. Now that
can support the unplugging but the ide-cs code is still not doing the
right things in this case (and the core could be a little more careful).
The ide_unregister can fail - you are supposed to call it again later if
it does - ide_cs doesnt
next prev parent reply other threads:[~2003-07-23 20:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 18:11 compact flash IDE hot-swap summary please Dave Lawrence
2003-07-23 18:18 ` Alan Cox
2003-07-23 19:49 ` Russell King
2003-07-23 20:13 ` Alan Cox [this message]
2003-07-23 21:15 ` Russell King
2003-07-23 22:15 ` Alan Cox
2003-08-14 0:21 ` Vojtech Pavlik
2003-07-23 19:12 ` Andre Hedrick
2003-07-23 19:51 ` Russell King
2003-07-23 19:48 ` Andre Hedrick
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=1058991230.5515.126.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=dgl@integrinautics.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.