Am Freitag, 4. Mai 2007 22:28 schrieb Alex Villacís Lasso:
> I think it was because I was taking the model from stir4200 and mcs7780,
> and it seemed to me that they followed this pattern. If this could cause
> any problems, I can rework the driver to only allocate in one of the
> functions (mo
Oliver Neukum escribió:
> Am Donnerstag, 3. Mai 2007 22:00 schrieb Alex Villacís Lasso:
>
>> - kingsun_net_open() allocates the URB and (in successful completion)
>> leaves the device in the open state. A suspend/resume cycle here will
>> submit rx_urb, but the interface is supposed to be ope
Am Donnerstag, 3. Mai 2007 22:00 schrieb Alex Villacís Lasso:
> - kingsun_net_open() allocates the URB and (in successful completion)
> leaves the device in the open state. A suspend/resume cycle here will
> submit rx_urb, but the interface is supposed to be opened.
Sorry, you are right. I misr
Oliver Neukum escribió:
> Am Donnerstag, 3. Mai 2007 18:35 schrieb Alex Villacís Lasso:
>
>> /* Coming out of suspend, so reset hardware */
>> static int kingsun_resume(struct usb_interface *intf)
>> {
>> struct kingsun_cb *kingsun = usb_get_intfdata(intf);
>>
>> if (kingsun->rx
Am Donnerstag, 3. Mai 2007 18:35 schrieb Alex Villacís Lasso:
> /* Coming out of suspend, so reset hardware */
> static int kingsun_resume(struct usb_interface *intf)
> {
> struct kingsun_cb *kingsun = usb_get_intfdata(intf);
>
> if (kingsun->rx_urb != NULL) usb_submit_urb(kingsun
Alan Stern escribió:
On the other hand, I doubt that the usb_reset_configuration() call is
needed. It merely duplicates what the USB core did a few moments earlier.
Why does your driver bother to do a Clear-Halt? It should not be needed.
Again, because stir4200 does it and I wa
On Wed, 2 May 2007, [UTF-8] Alex VillacÃÂs Lasso wrote:
> >> submit the interrupt urbs for either endpoint in the driver code, my
> >> callback
> >> code never gets called at all - not even to signal an error while
> >> submitting the
> >> urb.
> >>
> >
> > That never happens. The callbac
On Tue, 1 May 2007 [EMAIL PROTECTED] wrote:
> After a big delay, I am now trying to write a driver for my USB-to-Irda
> dongle.
> This device reports the following in lsusb:
>
> Bus 002 Device 002: ID 07c0:4200 Code Mercenaries Hard- und Software GmbH
> Device Descriptor:
> bLength
> Please notice that usbmon does log the IrDA discovery packet (the one that
> starts with ), only my code does not get called for any response
> on the
> send.
Is i possible that the device needs an init sequence you don't do?
> I welcome any critique on the driver code, whether or not
