Hi... I've been trying to learn as much about these SSDTs as I can before I actually submit a problem report (I want to try a little bit harder to fix the problem myself before begging again for help). I do have a couple of questions:
},
"HP16", Package() // bluetooth
{
//"UsbConnector", 255,
"portType", 2,
"port", Buffer()
{ 6, 0, 0, 0 },
},
In the above code, to what is the last sequence of numbers ( in red and blue) in reference? More specifically, what is the blue number? Is that corresponding port position in the unpatched IO registry using USBInjectAll.kext? Would entering an incorrect value here (e.g., saying HP16 was number 5 in the IOreg when it's actually number 6) prevent the port from working?
Also, I noticed that while the
"portType", 2, line is present for this internal port (my own Bluetooth is on HS13), it is not present for any of the physical USB ports in the SSDT files I've been reviewing. Is this a requirement/recommendation for better identifying internal ports? And what is the difference between "USBConnector" and "portType"?
And, finally:
"8086_a12f", Package()
{
"port-count", Buffer() {
26, 0, 0, 0 },
"ports", Package()
{
I'm assuming the number in red (26) refers to the number of ports injected by the USBInjectAll.kext with the raise port limit patch applied? If that is the case, and I used
this patch to raise my own limit, should that number be 24 (as opposed to 26, understanding that this patch goes away once the SSDT is confirmed as working)?