On Wed, 1 Mar 2006, David Brownell wrote:
>
> > > The "-EPROTO" is common after unplug, but that -EILSEQ suggests you
> > > have a real issue in the lh7a40x_udc driver ...
> >
> > Not necessarily. -EILSEQ is a normal code used by uhci-hcd when a CRC or
> > timeout error occurs on an IN transac
On Wed, 1 Mar 2006, Marc Singer wrote:
> What would be handy is if there was a log of the packets being sent by
> the usbtest code, and whether or not those packets had the expected
> result. Is there such a log somewhere? Does the dmesg output show
> this?
You can use usbmon. Read Documentati
Jamie,
The patch changes the behavior, but it still fails test 10. Now,
though, I get a bonafide error.
[EMAIL PROTECTED] ~/z/usb > sudo ./testusb -a -t 10
unknown speed /proc/bus/usb/002/012
/proc/bus/usb/002/012 test 10 --> 32 (error 32)
EPIPE?
Since this works for you, I'm going t
On Wed, Mar 01, 2006 at 03:34:12PM -0500, Jamie Guinan wrote:
> Marc,
>
> Below is a patch against 2.6.16-rc5, which works with CONFIG_USB_ETH
> and CONFIG_USB_ETH_RNDIS.
It looks like you found the same thing tha I did, the portc bits were
set incorrectly. I was kind of hoping that you hadn't
On Wed, Mar 01, 2006 at 10:04:48AM -0800, David Brownell wrote:
> On Wednesday 01 March 2006 9:27 am, Marc Singer wrote:
>
> > > Test #10 taking a few minutes? Sounds troublesome. If this is using
> > > an OHCI or EHCI host controller and you've compiled with USB_DEBUG,
> > > you'll find a /sys/
What would be handy is if there was a log of the packets being sent by
the usbtest code, and whether or not those packets had the expected
result. Is there such a log somewhere? Does the dmesg output show
this?
There is nothing in async when my test10 goes awry. There is a lot in
dmesg, but I'l
On Tue, 28 Feb 2006, Marc Singer wrote:
...
>
> The question is this: what is the simplest gadget to use for debugging
> a UDC driver? I started with the serial gadget because I figured it
> would be easy to verify that it is working.
Marc,
Below is a patch against 2.6.16-rc5, which works with
> > The "-EPROTO" is common after unplug, but that -EILSEQ suggests you
> > have a real issue in the lh7a40x_udc driver ...
>
> Not necessarily. -EILSEQ is a normal code used by uhci-hcd when a CRC or
> timeout error occurs on an IN transaction.
True, but it's usually an either/or: either you
On Wed, 1 Mar 2006, David Brownell wrote:
> > It's getting an error 84.
> >
> > Wed Mar 1 06:49:26 PST 2006
> > ** Control test cases:
> > test 9: ch9 postconfig
> > /proc/bus/usb/002/014 test 9, 55.293133 secs
> > test 10: control queueing
> > /proc/bus/usb/002/014 test
On Wednesday 01 March 2006 9:27 am, Marc Singer wrote:
> > Test #10 taking a few minutes? Sounds troublesome. If this is using
> > an OHCI or EHCI host controller and you've compiled with USB_DEBUG,
> > you'll find a /sys/class/usb_host/.../async dump of the control and
> > bulk queues. If it d
On Wed, Mar 01, 2006 at 07:39:06AM -0800, David Brownell wrote:
> On Wednesday 01 March 2006 1:09 am, Marc Singer wrote:
> > On Tue, Feb 28, 2006 at 10:29:03PM -0800, David Brownell wrote:
> > >
> > > http://www.linux-usb.org/usbtest/#gadgets
> > ...
> >
> > I'm not seeing an explanation of wha
On Wed, Mar 01, 2006 at 02:50:25PM +0100, Oliver Nittka wrote:
>
> Marc Singer wrote:
>
> > The only oddity I've seen so far is that the gadget wasn't detected
> > when the target (gadget) rebooted. I know that the driver has an
> > error in the USB power control. Perhaps that's at fault in the
On Wednesday 01 March 2006 1:09 am, Marc Singer wrote:
> On Tue, Feb 28, 2006 at 10:29:03PM -0800, David Brownell wrote:
> >
> > http://www.linux-usb.org/usbtest/#gadgets
> ...
>
> I'm not seeing an explanation of what the tests should look like. How
> long should each one last? Most take a
Marc Singer wrote:
> The only oddity I've seen so far is that the gadget wasn't detected
> when the target (gadget) rebooted. I know that the driver has an
> error in the USB power control. Perhaps that's at fault in the
> detection.
Hello Marc,
i wrote a fix for that, but it's not thoroughly
On Tue, Feb 28, 2006 at 10:29:03PM -0800, David Brownell wrote:
> On Tuesday 28 February 2006 9:48 pm, Marc Singer wrote:
>
> > The question is this: what is the simplest gadget to use for debugging
> > a UDC driver? I started with the serial gadget because I figured it
> > would be easy to verif
On Tuesday 28 February 2006 9:48 pm, Marc Singer wrote:
> The question is this: what is the simplest gadget to use for debugging
> a UDC driver? I started with the serial gadget because I figured it
> would be easy to verify that it is working.
Gadget Zero is designed to be the place to start; s
On Tue, Feb 28, 2006 at 10:29:03PM -0800, David Brownell wrote:
> On Tuesday 28 February 2006 9:48 pm, Marc Singer wrote:
>
> > The question is this: what is the simplest gadget to use for debugging
> > a UDC driver? I started with the serial gadget because I figured it
> > would be easy to verif
Thought I'd turn on the lh7a40x driver for grins and see what happens.
Turns out that it didn't even compile. Once that was fixed, it still
wouldn't connect using the serial gadget driver.
The first error I see, on connecting the USB cable, is
-> ERROR: gadget setup FAILED (stalling), setup re
18 matches
Mail list logo
