On Wed, Apr 29, 2020 at 4:06 PM Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > > On Wed, 29 Apr 2020, Andrey Konovalov wrote: > > > On Fri, Apr 10, 2020 at 5:53 PM Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > > > > > > On Fri, 10 Apr 2020, Andrey Konovalov wrote: > > > > > > > On Fri, Apr 10, 2020 at 2:29 AM Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > > > > > > > Something else: I've been testing raw-gadget with various UDCs that I > > > > have [1] and everything seems to work, except for emulating SuperSpeed > > > > devices with net2280. I've just found it out yesterday night, and > > > > haven't had a chance to debug that yet, but if you know about some > > > > potential issues I could encounter with SuperSpeed/USB3+, please let > > > > me know. > > > > > > Well, USB-3 has streams, unlike USB-2. You may want to think about > > > supporting them. > > > > Do I understand correctly, that to support streams I basically need to > > allow the user to set stream_id on the request being submitted? > > Yes, for bulk endpoints. One more question (sorry for so many :). Looking at other fields of usb_request struct I see frame_number. AFAIU it's filled in by the UDC driver for ISO transfers. Does it make sense to expose it to userspace? I don't see any composite/legacy gadgets use that field at all.
