Mikolaj Zuberek wrote:
| best position to shed some light on my problem. Any ideas why the
| usb-skeleton's probe function is called for some devices and not for
| others even if I have correct Vendor/Product ids hardcoded?
Is there another loaded driver that claims the device? If your hotplug
system is configured, it probably loads the appropriate driver and
prevents the USB subsystem from calling your probe function cause it's
already register by another driver.
You're right, there is actually another driver that is associated with the device when it's plugged in. Is it possible to change that for example by assigning some sort of priority to my driver, so when the matching device is plugged in my driver will be associated with that device in the first place?
Mikolaj
The information contained in this e-mail and in any attachments is confidential and is designated solely for the attention of the intended recipient(s). If you are not an intended recipient, you must not use, disclose, copy, distribute or retain this e-mail or any part thereof. If you have received this e-mail in error, please notify the sender by return e-mail and delete all copies of this e-mail from your computer system(s). Please direct any additional queries to: [EMAIL PROTECTED] Thank You.
------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
