Georg Acher wrote:
> > > If you mean control messages to EP0 work but not bulk to EP7, then only
> > > some problems with the configuration/alternate setting seem plausible to
> > > me.
> >
> > The latter off course. (control messages to EP0 work but not bulk to
> > EP7)
> > There is only one possible configuration, so that should be ok.
> > There are three possible alternate settings for the second interface, I
> > checked the setting with a USB_REQ_GET_INTERFACE control message and it
> > is also ok.
> > I am running out of idea's of things to try...
>
> Me too... Have you tried to clear the stall condition of EP7 with
> usb_clear_halt?
Yes, I did, no effect.
But that doesn't matter beacuse i have found out what the problem is.
I hooked up a CATC and behold!
The alternate interface set by me, specifies an out packet size of 32
bytes, and an in packet size of 64. (the alternative interfaces only
differ in the packets sizes...).
The linux machine however is sending larger packets (64 bytes).
So there is a bug there somewhere...
> > usb_set_interface(dev, 1, 2) should be enough to set the alternate
> > setting on the interface right ?
it should but apparantly isn't :-)
> > But it might be a side effect, because i am also getting other weird
> > things.
> > For example, sometimes after I unplug the device and unload the module
> > and replug it, all bulk transfers to the device block. (this is without
> > the module loaded, trying bulk tranfer from userspace...)
>
> Only bulk transfers, does this also happen to control transfers?
I haven't tried.
> > If this happens, i can plug and unplug the device as often as i like,
> > this condition only goes away on reboot. Even rmmod'ing and insmod'ing
> > the usbcore and usb-uhci driver modules doesn't work (only tried this
> > under 2.3.39 though...they are no longer modules now).
>
> Try the latest usb stuff, there were large patches in between.
ok. the problem has occured on 2.3.99-pre2, but i haven't tried the
loading/unloading... i will soon.
> > That is why I am suspecting there is a problem in the uhci module too...
> > triggered by something i do or something the device does ( the timeout
> > ?).
>
> You said that both uhci drivers show this behavior. That makes it a bit more
> unlikely that it is actually a problem in the HCD (but doesn't exclude
> it...)
Did i say that ?
I can't remember trying anything else than usb-uhci, certainly not with
2.3.99-pre2
I will upgrade to 2.3.99-pre3 today and play around with the different
drivers.
I'll let you know.
J.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
