On Wed, Oct 20, 2004 at 09:20:51AM +0100, Mikolaj Zuberek wrote:
Hi Greg,
You, as a developer of usb-skeleton driver, would probably be in the best position to shed some light on my problem.
And you, as modifier of the usb-skeleton driver, and possessor of the
device in question, are in the best position to post your modified
driver, and post the output of the kernel log when plugging in your
device
thanks,
greg k-h
The only changes I made to usb-skeleton.c code are those:
/* Define these values to match your devices */ #define USB_SKEL_VENDOR_ID 0x04B4 #define USB_SKEL_PRODUCT_ID 0x1002
As I said in the previous message, I noticed in the the kernel log output that another driver claims my device when it's plugged in. I'm wondering now if there is a way (apart from Vendor/Product ids) to make USB subsystem associate my driver with the device when it's plugged in.
Regards,
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
