On Fri, Jan 25, 2013 at 03:19:22PM +0100, Gerd Hoffmann wrote: > Hi, > > >> diff --git a/MAINTAINERS b/MAINTAINERS > >> index 8ae709e..c5b37de 100644 > >> --- a/MAINTAINERS > >> +++ b/MAINTAINERS > >> @@ -7911,9 +7911,10 @@ F: drivers/net/wireless/ath/ar5523/ > >> USB ATTACHED SCSI > >> M: Matthew Wilcox <willy@xxxxxxxxxxxxxxx> > >> M: Sarah Sharp <sarah.a.sharp@xxxxxxxxxxxxxxx> > >> +M: Gerd Hoffmann <kraxel@xxxxxxxxxx> > > > > Should Matthew be removed from this? > > Dunno, Sarah? > > > Also, any word on when I can remove the CONFIG_BROKEN marking on this > > driver? > > With the patches in -next uas itself should be reasonable solid. > > Problem is that uas is pretty much the only device using streams, > so uas will be the one who triggers any stream bugs in xhci. > I have no idea how solid xhci streams support is at the moment. > > Sarah, is there some way to avoid using streams? The UAS specs seems to > imply using streams is mandatory when connected to a USB-3 port, is that > correct? Is there some way to force usb3 devices into usb2 mode even > when plugged into a usb3 port? I'd like to have a no_streams module > option if possible ... Well, I think we want to use streams, that's the whole advantage of UAS over the old spec. I wasn't aware that the bugs were in the xhci driver, I thought they were in the uas driver, but I could be totally wrong. Oh, and any hints on what device on the market today actually follows the UAS spec so I can buy one for testing? thanks, greg k-h -- 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
