Anyway, I want my system to work with normal modems as well as with my custom one. So, I have ACM support and loading my own driver. My driver looks for a specific Vendor/Device ID, whicl ACM driver looks at device class when probing. When my modem is connected, ACM driver take control every time. Is there a way to stop this behaviour? I want my driver to probe for the modem before ACM driver does.
Just make your device not look like a CDC-ACM device ... that's the root of your problems. If it's not ACM, it shouldn't be declaring in its descriptors that an ACM drivers is the answer.
Alternatively, teach the ACM driver enough about your device that it'll blacklist it ... so no matter what order the probe() calls reach the drivers, ACM will know to ignore that model.
- Dave
------------------------------------------------------- This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek For a limited time only, get FREE Ground shipping on all orders of $35 or more. Hurry up and shop folks, this offer expires April 30th! http://www.thinkgeek.com/freeshipping/?cpg=12297 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
