It does look from the trace like the in-direction is getting to the device
first. You could enable the "urb tracing" in the javax.usb.properties
file to get more detailed tracing about each URB, but I'm pretty sure
everything looks right from the javax.usb perspective.
To get a bus trace, you
Sorry it took so long. Here is an attached devio.c file with debugging.
It's from the 2.6.11 kernel source.
To rebuild your kernel, first get the 2.6.11 source and extract it
somewhere (I'll assume you extract to /usr/src/linux-2.6.11/).
Then replace the drivers/usb/core/devio.c file with th
Quoting Dan Streetman <[EMAIL PROTECTED]>:
>
> Your emailer is line-wrapping the JNI trace...can you resend as an
> attachment?
Attached
> I just want to verify with the JNI trace that the in-direction buffer is
> getting submitted before the out-direction buffer. It looked like, from
> th
Your emailer is line-wrapping the JNI trace...can you resend as an
attachment?
I just want to verify with the JNI trace that the in-direction buffer is
getting submitted before the out-direction buffer. It looked like, from
the JNI trace you sent, that the out-direction buffer was getting sen
Quoting Dan Streetman <[EMAIL PROTECTED]>:
>
> I have to assume the device is really not sending the first response you
> are expecting. Without knowing the device protocol, I have no idea why
> your device would skip that.
At first I assumed it was a problem with a device itself. But like I
I have to assume the device is really not sending the first response you
are expecting. Without knowing the device protocol, I have no idea why
your device would skip that.
If you can get a USB bus trace, you could check if the device was actually
sending the first response (and so show that
It looks like the NPE is happening in your code, not javax.usb code. I
assume you're replacing the standard ClassLoader with your own? You
should check your "BundleClassLoader" line 291, that's where the NPE is
happening.
On Mon, 9 May 2005, Szabolcs Tahin wrote:
>Hello,
>
>just installed
Hello,
just installed the newest javax.usb package and enabled tracing. Here a
snippet with the exception. Can you recognize something wrong?
Szabolcs
[hotplug](3) JavaxUsbTopologyUpdater.c.build_device[112] Building device
/proc/bus/usb/001/001
[hotplug](3) JavaxUsbTopologyUpdater.c.build_dev
Hello,
I've run
into a similar problem that somebody has reported in April to the list.
My task is to deal with a USB prototype using an OSGi framework (like Oscar,
Knopflerfish).
I use the javax-usb 0.10.2, javax-usb-ri 0.10.2 and javax-usb-ri-linux 0.10.5
packages.
See below the exception. Any
