On Sat, 6 Dec 2003, Mathias Gug wrote: > >A distinct possibility is that the modem needs to be reset somehow in > >order for the new firmware to take effect. If that reset were failing, it > >could account for what you see. > > > > I've tried to reset all endpoints (0,5 and 7) and rescan the usb bus once > the firmware is uploaded and before sending the first control message. But > it doesn't solve the problem : I still get the USB control message timeouts.
Do you call usb_reset_device()? > Could it be possible that the firmware is buggy and that it doesn't > understand the fixes included in the later kernels ? (It is working with > kernels < 2.4.21-pre4 ). That doesn't seem likely -- if the firmware was buggy it probably wouldn't work with any kernel. But it might be worthwhile doing a detailed comparison of 2.4.21-pre3 and 2.4.21-pre4 to try and find the differences. Alan Stern ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
