Quoting Dan Streetman <[EMAIL PROTECTED]>: > If you put debugging higher than that, you might as well put it in the > usbfs layer. In that layer, the file you want is > "drivers/usb/core/devio.c" and the specific methods you want are > "proc_submiturb" (which takes your buffer and sends it to lower levels) > and "async_completed" (which is the callback - in interrupt - that the > lower levels call when the device returned data for your buffer).
I have added debugging to devio.c and it shows the same thing that javax.usb does, which means that it's not a problem with javax.usb. I tried to test it on different machine but the only other machine I have access to is Sun server with AMD x64 running redhat. Unfortunately, I was unable to get javax.usb working on 64 bit machine. I got it to compile with just a few warnings but it doesn't seem to like passing addresses between java and dynamic library. I don't think I can do anything else in the absence of hardware tracer, which is not something I want to pay for. At this point, I don't want to invest any more time into and I'll just have to work around it. Thank you for all you time and help. ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click _______________________________________________ javax-usb-devel mailing list javax-usb-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/javax-usb-devel
