Hi, > That's right. However, the oops you saw shouldn't happen so long as > intf->cur_altsetting points to something valid. I got the impression that > in the cdc-acm probe routine maybe it was a null pointer.
Yes, i think so too. > Can you insert > a statement in the cdc-acm probe function to print out the values of ifcom > and ifdata, to check that they aren't NULL? Already done, that's what helped me find this was related to altsettings stuff. I didn't check to see if cur_altsetting was null, but a dev_dbg() at the beginnning of the function was appearing, and not the dev_dbg() I had put after this block. > > I'm not sure the change in cdc-acm (which no longer uses index 0 > > altsetting) is correct. Or is this another bug in my phone (motorola C350) > > which should be handled differently than other cdc-acm devices ? > > It's hard to say without more information. The contents of > /proc/bus/usb/devices or the output of lsusb with the phone plugged in > would help. Ok, I'll try to do that tonight. -- Colin ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
