( I still had to poll linux-ide archives... )
>> Not by default. The dock driver immediately undocks unless
>> immediate_undock parameter is set to 0. Any access to the bay inside the
>> dock afterwards might freeze the system.
>>
>> Actually I was talking about the "bay not in the dock"-case here.
> In that case, the effect differs depending on the hardware. In the ideal
> universe, Thinkpad users flick out the eject lever and wait for a
> confirmation that they can pull out the drive. Dell and HP users have to
> request a safe remove in advance.
If you need to make clear that the user has to wait for a notification
before he removes the device, you could just make him clear that he has to
request a safe remove in advance.
But yes, I see your point.
>> There are those which do simple PCI hotplugging without the involvement of
>> ACPI (many/all HPs AFAIK) and those which present themselves as a
>> dockstation through ACPI (those with a _DCK method). The thinkpad X60 dock
>> I have here has the request button, too.
> Right. In that case, it needs to be possible for userspace to indicate
> that the eject request should not automatically destroy the device.
> Actually removing the dock should do so in all circumstances.
That's what I'm trying to say.
Just to make clear that we agree on the design, if so, I'll try to provide
a patch:
1. Dock event: libata immediately detaches the device
(libata will need another sysfs flag is_on_dock userspace can query)
2. Bay event: libata signals a BAY_EVENT through uevent, userspace writes
1 to /sys/.../device/delete
Regards,
Holger
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
