The pvrusb2 driver does not have any knowledge (or care) what port was used. It just gets loaded and given an endpoint when the hardware appears. The pathway between the driver and the hardware is completely managed by the USB stack. The topology is invisible to the driver.
Likely everyone already knows that. Just want it to be clear. -Mike On Sat, 16 Mar 2019, Gary Buhrmaster wrote: > On Sat, Mar 16, 2019 at 5:52 PM Jan Ceuleers <[email protected]> > wrote: > > > The third most common issue is USB connectors needing reseating. > > One can discuss order, but kernel USB drivers > (which change at almost every kernel release) > are also a common issue, but in the case of > the USB drivers and the cables I consider those > cases as being more that the HVR-195xs is a > victim, not directly responsible. But they can > all result in the same symptom of hangs or > other artifacts, so yes, they should be included. > And to add to that, sometimes moving the cable > to a different PC port solves issues (because the > sharing that is happening elsewhere is not working > quite right). The joys of layering. > _______________________________________________ > pvrusb2 mailing list > [email protected] > http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2 > -- Mike Isely isely @ isely (dot) net PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8 _______________________________________________ pvrusb2 mailing list [email protected] http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
