On Mon 19. Mar - 13:22:43, Matthew Garrett wrote:
> On Sun, Mar 18, 2007 at 09:27:51AM +0100, Holger Macht wrote:
>
> > I don't prefer any solution, whether doing it inside the kernel, or doing
> > it in userspace. What would be good would be to know what's the 'right'
> > way to go, or at least what both kernel people and userspace people can
> > agree on so that we can find a solution across distributions, whatever.
> > I'm currently just looking how to integrate the generic dock and bay
> > driver into the openSUSE distribution, and this seems to be quite hard,
> > especially because of the above mentioned already working solution ;-)
>
> If the kernel knows that a bay device has just been added or removed, it
> makes sense for the device removal to take place in the kernel rather
> than bouncing it out to userspace and then back into the kernel. Pulling
> out a cardbus card doesn't require us to run a userspace helper to
> detach the hardware.
Yes, makes sense to me. So if this is the way to go, we would need two
things:
1. libata integration into the bay driver
2. The dock station driver has to inform the bay driver that an undock
event took place, right?
But you still have to deal with mounted filesystems, no matter if it a
cardbus or a cdrom. Wouldn't we need something like 'save removal'
triggered from userspace like you maybe know from 'the other' operating
system?
Regards,
Holger
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
