On Thu, 2002-06-06 at 00:24, David Brownell wrote: > > So, why dies it give up? The diagnostic should give the status code. > Just knowing some call fails isn't so useful, but knowing _why_ it > does so is half way to knowing what's wrong.
All I can do is put some printk's to see what did it return, unless you give me more specific pointers. I am not even close to understand kernel coding. > > More likely a problem in the conversion of those drivers to use > that framework, or perhaps a longstanding bug at the HID level > that's now being detected (like an illegal argument). > And how can I verify it? > - Dave > _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
