On Sat, 8 Sep 2012, Hans de Goede wrote:
> Apps which deal with devices which also have a kernel driver, need to do
> the following:
> 1) Check which driver is attached, so as to not detach the wrong driver
>(ie detaching usbfs while another instance of the app is using the device)
> 2) Detach
On Wed, 22 Aug 2012, Hans de Goede wrote:
> >> + if ((dc.flags & USBDEVFS_DISCONNECT_CLAIM_IF_DRIVER) &&
> >> + strncmp(dc.driver, intf->dev.driver->name,
> >> + sizeof(dc.driver)) != 0)
> >> + return -EBUSY;
> >> +
> >> +
Hi,
On 08/22/2012 05:05 PM, Alan Stern wrote:
> On Wed, 22 Aug 2012, Hans de Goede wrote:
>
>> Apps which deal with devices which also have a kernel driver, need to do
>> the following:
>> 1) Check which driver is attached, so as to not detach the wrong driver
>> (ie detaching usbfs while anot
On Wed, 22 Aug 2012, Hans de Goede wrote:
> Apps which deal with devices which also have a kernel driver, need to do
> the following:
> 1) Check which driver is attached, so as to not detach the wrong driver
>(ie detaching usbfs while another instance of the app is using the device)
> 2) Detac
Hi,
Thanks for the review!
On 08/22/2012 02:04 PM, Oliver Neukum wrote:
> On Wednesday 22 August 2012 13:42:47 Hans de Goede wrote:
>> Apps which deal with devices which also have a kernel driver, need to do
>> the following:
>> 1) Check which driver is attached, so as to not detach the wrong dri
On Wednesday 22 August 2012 13:42:47 Hans de Goede wrote:
> Apps which deal with devices which also have a kernel driver, need to do
> the following:
> 1) Check which driver is attached, so as to not detach the wrong driver
>(ie detaching usbfs while another instance of the app is using the dev
