On Tuesday, December 10, 2013 4:48 AM, Bernd Porr wrote: > I've just checked out after a while the newest RC kernel and the > usb-auto config/attach is broken. Seems so that the driver specific usb > attach is no longer called and no firmware is loaded. Hartly, can you > point me to the code bits which should call the driver spcific attach or > give a short summary how that should work? I had a look at the git logs > but there are quite lot of subsequent changes. Can you give me some > guidance because it has changed a lot since I had a look at it the last > time. I don't have much time this week but can crack on next week re > that and test that thoroughly. Just now none of my DUX boards work at > all. They all have the same problem that there are zero subdevices and > the firmware is not loaded so I assume that the driver specific attach > is not called. Hello Bernd, I'm not sure why the usbdux drivers are not auto attaching correctly. Sorry about the problems. What version of the kernel are you testing with? Are the USB_DEVICE() id's correct in the driver? The comedi USB drivers should auto attach when the device is detected. The USB driver (*probe) will call comedi_usb_auto_config() which then calls the comedi driver (*auto_attach). All of the usbdux drivers do the initial USB setup, buffer allocation etc., then call comedi_load_firmware() to request and load the firmware for the device. After that the subdevices are allocated and initialized. Try putting a couple printk debug messages in the usb (*probe) and comedi (*auto_attach) functions in the drivers. You might also put a printk in the callback functions that actually upload the firmware to the device. Please let me know what you find. Hopefully this is a minor bug and we can resolve it quickly. Thanks, Hartley _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
