atom feed22 messages in org.freebsd.freebsd-usblibusb usb_interrupt_read hangs under...
FromSent OnAttachments
Xiaofan ChenApr 3, 2007 11:54 am 
Hans Petter SelaskyApr 3, 2007 12:26 pm 
Xiaofan ChenApr 3, 2007 1:34 pm 
Hans Petter SelaskyApr 3, 2007 2:42 pm 
Xiaofan ChenApr 3, 2007 11:55 pm 
Hans Petter SelaskyApr 4, 2007 7:37 am 
Xiaofan ChenApr 4, 2007 11:34 am 
Xiaofan ChenJul 4, 2007 5:32 pm 
Hans Petter SelaskyJul 5, 2007 3:24 pm 
Xiaofan ChenJul 8, 2007 12:25 am 
M. Warner LoshJul 8, 2007 5:11 am 
Xiaofan ChenJul 8, 2007 1:16 pm 
Xiaofan ChenJul 8, 2007 4:31 pm 
M. Warner LoshJul 8, 2007 8:00 pm 
Hans Petter SelaskyJul 9, 2007 4:35 pm 
Xiaofan ChenJul 10, 2007 1:27 am 
Xiaofan ChenJul 13, 2007 10:32 pm 
Hans Petter SelaskyJul 15, 2007 9:18 am 
Xiaofan ChenJul 16, 2007 3:44 pm 
Hans Petter SelaskyJul 17, 2007 5:55 am 
Xiaofan ChenAug 11, 2007 4:45 am 
Xiaofan ChenSep 22, 2007 3:47 am 
Subject:libusb usb_interrupt_read hangs under FreeBSD
From:Xiaofan Chen (xiao@gmail.com)
Date:Aug 11, 2007 4:45:36 am
List:org.freebsd.freebsd-usb

On 7/15/07, Hans Petter Selasky <hsel@c2i.net> wrote:

On Saturday 14 July 2007 00:33, Xiaofan Chen wrote:

Sorry that I have three more questions: 1) What is the correct method to correctly respond to clear halt feature request in the firmware so that it can still recover from the stall?

The USB 2.0 specification is not very clear about what the clear-stall command should do. It almost says that this is device dependant.

I think that clear-stall should only clear the data-toggle ! It should not clear any buffers. That should be done by a seperate control transfer.

2) For the host, how does it know that the buffer data is still correct if the buffer is not cleared?

Clear stall should only clear the data toggle!

You need a second control command to reset the buffers and/or the protocol!

2) What cause the stall to happen in the first place?

It is either a wrong data-toggle bit or a protocol error. The device can send stall at any time!

I guess that the stall might be related to the different behavior of Linux and FreeBSD implementation.

http://lists.alioth.debian.org/pipermail/libhid-discuss/2007-April/000121.html Charles Lepple mentioned the following. <quote> "The limitations that I have seen are due to different interpretations of interrupt requests. Linux usbfs submits one URB per libusb usb_interrupt_read/write request, and *BSD ugen seems to set up a recurring transfer (and libusb reads the buffer that is filled by those transfers).

This is fine as long as the libusb client program reads the buffer fast enough, but it does not allow you to submit interrupt requests at a slower rate than the descriptor specifies in *BSD."

</quote>

Is this the possible reason causing the STALL?

Xiaofan