On Thu, Oct 21, 2004 at 09:51:14AM +0100, Mikolaj Zuberek wrote: > >On Wed, Oct 20, 2004 at 09:20:51AM +0100, Mikolaj Zuberek wrote: > >>>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 > > > 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
I'm sorry, but I'm missing the kernel log part of the request I made above. Did you forget to attach it? > 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. Please see the usb documentation for the different types of ways to specify a usb device. It is in the kernel tree and can be generated by doing a 'make psdocs'. If another driver is grabbing your device, just don't build it :) good luck, greg k-h ------------------------------------------------------- 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
