On Thu, Jun 15, 2000, Mark Douglas Corner <[EMAIL PROTECTED]> wrote:
>
> Hi, I have a bug in a usb driver I wrote and I would like some advice.
>
> First things: 2.2.15 with most recent backport using usb-uhci.o
>
> The top level bug is a timeout on a usb_control_msg.
>
> On my CATC analyzer the setup packet for the control msg looks precisely
> as it does under windows. However, the next thing it should do is an OUT
> and actually send the control message. This never happens. In fact
> I get nothing on the analyzer at all, no syncs or anything.
This is bad. Do you get anything in the logs. If the HC isn't starting
new frames then it may have locked up. It usually tells us this happened
tho.
> So I dug into the code until I got stuck. In usb-uhci.c in the
> uhci_submit_control_urb there are clearly three sections one for the
> SETUP, one for the OUT and one for an IN for status.
>
> I put in a uhci_show_td call for each td. Each one looks mostly correct:
> one SETUP, one OUT, one IN.
>
> There are one or two strange things though:
>
> The MaxLen on the SETUP is 07 and the MaxLen on the OUT is 02.
> My setup packet is 8 bytes of data and my out packet is 3 bytes of data.
> Important? Also it says that Len=00 for all of them
That's fine. The length we program in the TD is the actual length - 1.
0x7FF for 0.
> Also, there is a TD Link Terminate printed out by the show_td.
>
> Any idea what is going on? Thanks.
Who makes your UHCI controller?
Does it have the same problem with the Alternate UHCI driver?
JE
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
