t1...@protonmail.ch (Tinker), 2018.07.27 (Fri) 12:17 (CEST): > (Also note that the USB 3 stack separately is unstable, and maybe
For the archives: That statement is wrong, unless all the dozens of terabytes I've moved over xhci(4) are broken now. Do you mean the isochronous transfer thing? CVS log says: ---------------------------- RCS file: /cvs/src/sys/dev/usb/xhci.c,v revision 1.77 date: 2017/09/08 10:25:19; author: stsp; state: Exp; lines: +202 -25; commitid: 6181T4xfBI8wUv3E; Add support for isochronous transfers to xhci(4). This is just a step forward which allows further progress to happen in-tree. The isochronous code path remains disabled for now. Playing audio over xhci(4) does not work properly yet, and I haven't even tested video input. Based on a work-in-progress diff by mpi@ from 2015. ok mpi@ ---------------------------- revision 1.82 date: 2018/04/27 13:25:08; author: mpi; state: Exp; lines: +72 -19; commitid : qNZkEhEejAdtaRlW; Introduce an helper function to extract endpoint's max burst value. Use this helper to calculate the Transfer Burst Count (TBC) and Transfer Last Burst Packet Count (TLBPC) required for isochronous support. Note that SS companion descriptors are still not read. While here print the ETE and IST values in debug mode. ---------------------------- Marcus
