Set up the context correctly for a high->full->low cascade of devices
The context setup code had misinterpreted the XHCI spec's wording when working out the TT hub slot/TT port number; they should refer to the hub where the high speed hub is, not the adjacent hub. This caused problems with some older KVMs (which are typically full speed, and often have low speed keyboard or mice connected). USBDriver would try to get the HID descriptors but actually sent garble to the device at the wrong speed. From NetBSD revision 1.83, and NetBSD PR/52791. Fixes Elesar ticket 80E-056-86AB5, where a Trendnet TK-409 caused a hang at power up. Version 0.25. Tagged as 'XHCIDriver-0_25'
Showing with 45 additions and 38 deletions