On Wed, 11 Nov 2003, Henry Culver wrote:
>It seems that after a successful call, urb->dev is getting set to 0.
This happens with 2.4.x and newer; it didn't happen with 2.2.x.
I don't know why the change was made.
>In my write_callback routine I simply re-set urb->dev to its correct
>value (which
On Tue, Nov 11, 2003 at 06:45:43PM -0700, Henry Culver wrote:
>
> It seems that after a successful call, urb->dev is getting set to 0.
>
> In my write_callback routine I simply re-set urb->dev to its correct
> value (which is stored in the private device structure) and the
> subsequent calls us
Replying to my own post ...
I've found a way to make my code work without having to
deallocate / reallocate the urb.
It seems that after a successful call, urb->dev is getting set to 0.
In my write_callback routine I simply re-set urb->dev to its correct
value (which is stored in the private d
On Tue, 2003-11-11 at 15:23, Alan Stern wrote:
> On Tue, 11 Nov 2003, Henry Culver wrote:
>
> > I am in the process of writing a device driver for a device which is a
> > combination vacuum flourescent display and ir receiver. The driver is
> > functional, but has some problems.
> >
> > The dev
On Tue, 11 Nov 2003, Henry Culver wrote:
> I am in the process of writing a device driver for a device which is a
> combination vacuum flourescent display and ir receiver. The driver is
> functional, but has some problems.
>
> The device has a single configuration, and single interface with 2 e
I am in the process of writing a device driver for a device which is a
combination vacuum flourescent display and ir receiver. The driver is
functional, but has some problems.
The device has a single configuration, and single interface with 2 endpoints.
The endpoints are transfer type "interrupt
