From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Brownell Date: Wed, 28 Feb 2001 16:56:25 +0000 Subject: Re: Adding PCMCIA support to the kernel tree -- developers needed. Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org > From: "David Hinds" > Sent: Monday, February 26, 2001 11:56 PM > > On Mon, Feb 26, 2001 at 09:47:49AM -0800, David Brownell wrote: > > > Exactly what is meant by "eject" though? "eject pcmcia-slot-1" > > can't exactly eject the drive, as it would for a CD or ZIP disc. > > Actually some PCMCIA sockets do have eject mechanisms. Powerbooks for > example. Does "cardctl eject 1" physically eject on those platforms? > > I think what's meant is "disconnect the drivers and do electrical > > shutdown". > > This was mostly what I had in mind. Good. Seems like for PCI, we'll need to pay attention to the user feedback mechanisms, since this is important for the high availability hotplugging mechanisms (cPCI, Compaq "Hotplug PCI") that use indicator LEDs to help protect that mission-critical data, while we recently learned that some folk really like beeps on PC-Card form factor devices. Without having looked at this, I'd like to think that the "quiesce the driver and hardware" functionality should be one code path, and the "give the right domain-specific feedback" paths might need to be different ... though I'd hope not. I think some of the patches Compaq put up on their hotplug site related to this stuff. - Dave _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel