Re: Restricting CDC-ACM devices

[Greg KH <greg@kroah.com>]

On Wed, Aug 22, 2007 at 09:41:33AM -0500, Nate wrote:
> 
> > Why do you not want to modify the driver?
> 
> Modifying the cdc-acm driver is an alternative; however, I would like to
> avoid that when I'm adding my vendor specific restrictions.  My hope is
> that when patches are made to that file, I don't need to worry about
> someone merging them over the my previous ones.  Is this a bad goal?

Well, just messing with the device ids is not that tough of a patch to
keep up to date over time, so you might just try that if necessary.

> > You can disconnect the device from the driver from userspace for any
> > device you just don't want to have connected by using the sysfs
> > bind/unbind files.  That doesn't require any kernel changes at all.
> 
> I don't fully follow you here.  Are you saying that I can disconnect the
> CDC-ACM driver from my USB device and allow my driver to get a call probe?

Yes.  You can manually bind and unbind all PCI and USB devices from
their drivers from userspace.  So you do have full control over this
already, no kernel changes needed.

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/