On Mon, Jun 18, 2001, Werner Cornelius <[EMAIL PROTECTED]> wrote:
> On Monday, 18. June 2001 19:33, Greg KH wrote:
> > On Mon, Jun 18, 2001 at 03:00:30PM +0200, Werner Cornelius wrote:
> > > Hello,
> > >
> > > I just programmed a new driver for a USB ISDN TA.
> > > I tested it with kernel versions 2.2.19 and 2.4.5 8uhci and ohci configs.
> > > Unfortunately some other persons testing the driver too reported that
> > > when using the alternate JE uhci driver with 2.4.5 the machine hangs when
> > > the driver is loade and a device is connected.
> > > Regarding 2.2.19 and 2.4.5 (uhci non je and ohci) no problems occured.
> > > Does anybody know what is the difference when using the uhci je driver
> > > instead of the standard uhci version ?
> > >
> > > What could be the reason ?
> >
> > Bulk queued urbs still do not work properly with the uhci.o (JE) driver.
> > usb-uhci.o (non-JE) works fine for these urbs. If your driver is using
> > queued urbs, this could be the problem.
>
> The driver does not queue urbs for the same endpoint, but uses other
> endpoints on the same device in conjunction.
> The device needs a maximum of 3 bulk-outs and 4 interupt ins which may be
> active at the same time, but it is always ensured that not more then one urb
> is outstanding for a single in or out endpoint. Additionally control
> transfers are occuring, too. Perhaps there might be some side effect from the
> fact you described.
> I think the driver users should be informed that the JE should not be used
> with this device.
Why shouldn't it be used with that device?
What Greg described and what you described are completely different.
JE
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
