Re: Restricting CDC-ACM devices

[Nate]

Thank you for your responses.  Please don't take my repeated questioning
of your answers as me being difficult, I'm just trying to get a better
understanding.


> 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.

That is a good point.  I may also be adding some extra logic to check
other fields to confirm compatibility before allowing a usb device to be
bound to the CDC-ACM driver.  That is still probably pretty small piece of
code in the probe function, but I'm just concerned that over time more
logic would be added and other developers will be maintaining the code.


> 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.

Does this require my userspace applications to poll the USB devices
(/proc/bus/usb/devices) and then disconnect/connect my driver every time a
USB device using CDC-ACM is connected?  Is this what is normally done? 
Does this cause a noticeable performance hit when the driver is cycled
like this?  If I don't enable CDC-ACM in make menuconfig, can I still bind
it to a USB device from userspace?


I don't know if this matters, but I wanted to add some use case details:
This driver will be running on a <200 MHz processor and there can be a
number of connects/disconnect of the device in a short time from the
users.

Thanks,
-Nate

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