Thanks Greg Greg KH <greg@...> writes: > Have you tried the 2.6.34 kernel instead? I've tried 2.6.34-rc7 from sarah and 2.6.34-rc6. the 2.6.34 kernel mainline must need the some patches for the function: usb_alloc_streams and usb_free_streams etc. > What does the data show is happening? Perhaps your device really didn't > send anything? Maybe it is true. But when the stream_id is set to "1" in the host driver. The device still get "0xffff" and the NUMP is still "0". I think device won't send anything because of this reason. But it made me puzzled "how xhci transport these buffer". And the problem becomes why the stream_id changed? > Do you have a pointer to the source of your driver so we can verify you > are setting everything up properly? What type of driver is this? It is a usb mass storage driver from MCCI. The uasp driver code has been submit, which is waiting for your approvement. Thanks very much! Darian -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
