public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	len.brown@intel.com
Subject: Re: patch [0/2]: acpi: add generic removable drive bay support
Date: Sat, 09 Sep 2006 16:15:44 +0100	[thread overview]
Message-ID: <1157814944.6877.35.camel@localhost.localdomain> (raw)
In-Reply-To: <20060907161305.67804d14.kristen.c.accardi@intel.com>

Ar Iau, 2006-09-07 am 16:13 -0700, ysgrifennodd Kristen Carlson Accardi:
> the exact same event for either insertion or removal (i.e. the Dell M65 for
> example).  Same scripts for using these events and udev can be found on the
> thinkwiki website:
> 
> http://www.thinkwiki.org/wiki/How_to_hotswap_UltraBay_devices#When_using_the_ata
> _piix_driver

drivers/ide/piix does not support hotplug of any kind. drivers/ide does
not support hotplug of any kind. There is an ioctl hack that vaguely
works now and then for some interfaces but it too is completely unsafe
in 2.6 except for RHEL4. If people keep trying to post suggestions to
use them for anything but debugging I'm going to have to send Andrew
patches to remove them entirely before more people lose their data.

RHEL4 has a set of locking changes/patches to support some basic hotplug
cases, they were refused upstream so upstream simply doesn't support it.

Alan


      parent reply	other threads:[~2006-09-09 14:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-07 23:13 patch [0/2]: acpi: add generic removable drive bay support Kristen Carlson Accardi
2006-09-08  1:34 ` Nigel Cunningham
2006-09-08 17:48   ` Kristen Carlson Accardi
2006-09-08 19:59   ` Matthew Garrett
2006-09-08 19:58 ` Matthew Garrett
2006-09-08 20:21   ` Kristen Carlson Accardi
2006-09-08 20:33     ` Dave Jones
2006-10-14  5:13       ` Len Brown
2006-09-08 20:42     ` Matthew Garrett
2006-09-09 15:15 ` Alan Cox [this message]

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=1157814944.6877.35.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=kristen.c.accardi@intel.com \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --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