Hi, I added an entry (not intelligently) in the statically defined blacklist within the hid-core.c file in order to exclude hidcore of probing and matching to my driver, of cource i had to rebuild the kernel. Is there a way to exclude the usbhid driver on matching to a device, in an other way? Maybe an addition in the modprobe.conf file? ( Just a thought). In the man page of the modprobe.conf is suggested that a use of the blacklist command would ignore "all of a particular module's internal aliases". Does that mean that it will ignore all of the blacklist entries already statically added inside the code? ----- Original Message ----- From: "Greg KH" <greg@xxxxxxxxx> To: "Makrydakis Giannhs" <makryd@xxxxxxxxxx> Cc: <kernelnewbies@xxxxxxxxxxxx> Sent: Monday, August 21, 2006 4:34 AM Subject: Re: Driver matching > On Sun, Aug 20, 2006 at 10:17:16PM +0300, Makrydakis Giannhs wrote: >> >> >> I wrote a usb device driver for a HID device, have done the compilation >> and >> inserted this module in the kernel. the problem is when i start the >> device >> it gets matched on the usbhid driver instead of my vendor_and_product >> specific driver. What didn't I get right? > > You forgot to add your device to the hid driver's blacklist so it would > not bind to your device first? > > Hope this helps, > > greg k-h > > -- > Kernelnewbies: Help each other learn about the Linux kernel. > Archive: http://mail.nl.linux.org/kernelnewbies/ > FAQ: http://kernelnewbies.org/faq/ > -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
