Hi Michal, While running USB CV MSC tests I found that the wIndex parameter sent by the USB CV application is not matching the fsg->interface_number in function fsg_setup() for USB_BULK_RESET_REQUEST and USB_BULK_GET_MAX_LUN_REQUEST cases in file f_mass_storage.c. This is with Android Gadget. This is a composite gadget with RNDIS(interface 0 and 1), UMS (interface 2) and ADB interfaces. Note that wIndex passed from USB CV is 0x0 while fsg->interface_number is 0x2 (since UMS is interface 2). As a result a check (w_index != fsg->interface_number) fails and the USBCV test reports a failure. If the UMS is the first interface and rndis is kept at the end, USB CV MSC test works as expected. Why is the interface_number incorrectly sent by USBCV? Any pointers will be really helpful. Also I saw in mail archives that RNDIS works reliably only when it is assigned interface 0 and 1. Is this a Windows issue? Is interface order so important? Regards, Maulik -- 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
