Hello List,
On Wed, 15 Sep 2004 08:59:57 -0700, David Brownell <[EMAIL PROTECTED]> wrote:
On Wednesday 15 September 2004 8:21 am, Christoph Torens wrote:
But then I noticed that with the following DEBUG module parameters everything works perfectly (the first three parameters are standard).
options hc_isp116x hcport=0xf4000000 hcport2=0xf4000002 irq=25 hc_verbose=1 hc_error_verbose=1 urb_debug=2
That's usually a sign of the driver not handling the hardware correctly, so that the extra delays caused by kernel printk change the driver timings enough to dodge a race...
So, I have tested a few things, I removed the debug messages one by one and now I have isolated the one that causes the working or not working of the driver. What can I do next?
The debug message is in the function: hci_submit_urb I guess this means this function is buggy. But I have absolutely no idea what to do. And if it's a timing problem with these debug messages, how could this be fixed anyway?
-- Regards, Christoph
------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
