Dmitri wrote: >Quoting Ravi Kumar B S <[EMAIL PROTECTED]>: > >>Dmitri wrote: >> > >>>In worst case, presence of printk's moves the memory around, and you have >>>a stray pointer somewhere that reads or writes past the allocated >>>memory. With printks in place, this pointer happens to point to a safe >>>place; without them all fails. >>> > >>thanks. but the thing is that the cleaned up code works on another of my >>machine. and is not working only in a particular machine. i see the >>configuration as same in both the machines. >> > >I doubt you have two *identical* computers. If you are accessing the wrong >memory then the content of that memory is important. But in any case, if >I were you, I would review the diffs between two sources first, and if I >can't see anything obvious I would put some of printk back to see what >happens (or to remove some from the other source). > >Dmitri > hi i found why the driver is not listed as being used. when i connect the device. the probe function is getting called. in that first it makes check on the device class signature. there it is immediately returning as i am getting 0 as the class signature. this is what the error i am getting. bt_usb: - class signature 0, 0, 0 did not match.
so next when i do lsmod, the driver is listed but not being used. so natureally the open call is also failing. any idea what could be wrong? /Ravi kumar b-s _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
