On 06/26/2013 02:20 PM, Paul Zimmerman wrote: >> From: Stephen Warren [mailto:swarren@xxxxxxxxxxxxx] >> Sent: Wednesday, June 26, 2013 12:13 PM >> >> On 06/24/2013 12:34 PM, Paul Zimmerman wrote: >>> I screwed up the sense of this if() statement while porting our >>> vendor driver to create the dwc2 driver. This caused frame overrun >>> errors on periodic transfers when there were other transfers >>> active in the same (micro)frame. >>> >>> With this fix, the dwc2 driver now works on the Raspberry Pi >>> platform even with the USB Ethernet controller enabled, where >>> before that would cause all USB devices to stop working. >> >> Ooh, that sounds exciting. Does it work in the upstream/mainline kernel, >> or just the Raspberry Pi Foundation's downstream kernel though? > > I only tested with the Raspberry Pi Foundation's kernel, by replacing > the dwc_otg driver with the dwc2 driver, using that customized platform > interface I sent to some of you guys a while back. I didn't do a lot of > testing, just checked that I could access the web without causing any > noticeable problems. > > I hope whoever is supporting the Pi in the mainline kernel will try adding > dwc2 support now that it seems to be working. I'm not sure who that would > be, though. Well, it appears to work! I tested it on both a model A and B (rev 2) and devices enumerate on the bus OK now. I haven't actually tested data transfer yet though. -- 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
