Le Samedi 15 Janvier 2005 13:40, Remi Collet a écrit : > Modifying from usb_unlink_urb(..) to usb_kill_urb(..) in the source of > the driver is possible (1 found it 6 times) but someone must analyse the > code to see if URB_ASYNC_UNLINK is set (i'll have to look in the devel > branch) >
It is indeed : eu_eth.c:239: ins->urb_write->transfer_flags &= ~URB_ASYNC_UNLINK; eu_eth.c:499: ins->urb_write->transfer_flags |= URB_ASYNC_UNLINK; eu_eth.c:502: ins->urb_oam_write->transfer_flags |= URB_ASYNC_UNLINK; eu_main.c:955: ins->urb_int->transfer_flags &= ~URB_ASYNC_UNLINK; eu_main.c:1050: ins->read_urb[i]->transfer_flags &= ~URB_ASYNC_UNLINK; eu_main.c:1072: ins->urb_write->transfer_flags &= ~URB_ASYNC_UNLINK; eu_main.c:1079: ins->urb_oam_write->transfer_flags &= ~URB_ASYNC_UNLINK; eu_utils.c:438: qhead->urb->transfer_flags &= ~URB_ASYNC_UNLINK; macros.h:107:#define URB_ASYNC_UNLINK USB_ASYNC_UNLINK Pipes.c:658: ins->read_urb[i]->transfer_flags &= ~URB_ASYNC_UNLINK; Pipes.c:923: urb->transfer_flags &= ~URB_ASYNC_UNLINK; Can you elaborate on the impact ? Cheers, -- Alexis Deruelle <[EMAIL PROTECTED]>
