Oliver Neukum wrote:
> Hi,
>
> is this really needed ?
Yes, there need to be some hooks whereby user mode code
can affect driver binding. There are cases where user
mode drivers are preferred, and there have also been
cases where the wrong kernel mode driver kicked in.
> case USBDEVFS_DISCONNECT:
> driver = ifp->driver;
> if (driver) {
> down (&driver->serialize);
> dbg ("disconnect '%s' from dev %d interface %d",
> driver->name, ps->dev->devnum, ctrl.ifno);
> driver->disconnect (ps->dev, ifp->private_data);
> usb_driver_release_interface (driver, ifp);
> up (&driver->serialize);
> } else
> retval = -EINVAL;
> break;
>
> The race is there by design. You cannot guarantee that a
> device will still be unbound.
At which point it can be detected in user mode, which
should then recover appropriately.
- Dave
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
