On Fri, Aug 28, 2009 at 02:21:50PM -0400, Tim Thomas wrote: > I am using a moblin developer's version, 2.6.30.3-4.moblin2-netbook, and > I am working on a USB driver for a Bluetooth Dongle. I have compiled > and 'insmod'ed the driver. When the device gets plugged in, the > built-in kernel driver, which I assume is btusb.ko, claims the device > and my probe function never gets called. I would have assumed that a > module that gets loaded into after boot would be inserted into the head > of the list to allow the built0in drivers to be over-ridden.
No, the kernel works the other way around, "first in" is allowed to grab the device. > How do I get my probe function called before the system grabs the > device? Add a blacklist entry into the btusb driver in the kernel package to prevent it from grabbing your device. Or, from userspace, unbind from the btusb driver, and then bind to yours. Why do you need to write a new bluetooth usb driver, what's wrong with the one in the kernel today? Is it not working for you in some way that we should fix it? thanks, greg k-h _______________________________________________ Moblin dev Mailing List [email protected] To manage or unsubscribe from this mailing list visit: http://lists.moblin.org/listinfo/dev or your user account on http://moblin.org once logged in. For more information on the Moblin Developer Mailing lists visit: http://moblin.org/community/mailing-lists
