Thanks everyone. Here are some responses: On Wed, Sep 16, 2015 at 4:33 PM, Greg KH <greg@xxxxxxxxx> wrote: > Really? I thought you said the error was in the xhci driver, not ehci, > for 3.14. We tested with both and it failed with both, sorry for not being clear. > Can't you just plug your device into a desktop running a 4.2 kernel to > see what it does? It actually does work with 4.2, so if all else fails we may update to this kernel. On Thu, Sep 17, 2015 at 8:49 AM, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > If the problem affects both the EHCI and xHCI controllers, why do you > want to work around by changing only xhci-hcd? Wouldn't it be better > to change the USB core? We're looking into this and have realized this is probably the best place to make a patch, thank you. > What type of endpoint is this, anyway (control, bulk, interrupt, or > isochronous)? We're using an isochronous transfer. On Thu, Sep 17, 2015 at 12:57 PM, Fabio Estevam <festevam@xxxxxxxxx> wrote: > You could just build 4.2 or 4.3-rc1 manually and deploy it. > > We use Yocto with kernel 4.1 without issues. Thanks, we may try this if we don't get a patch up and running. Thanks again, Todd -- 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
