Hold on...
I used Corpnewt USBmap in Big Sur and Monterey and it got my maps built. It doesn't need USBInjectAll nor XhciPortLimit quirk to do the mapping.
This is the first lore I've noticed that Catalina or earlier is required...
Does the most-referenced Guide to USB Portmapping here say something about a macOS version limit? I missed that (I'm not going to re-peruse that guide, so maybe it does and I missed it)
What gives?!
My recent post history includes some hints about using USBmap to fill in the somewhat ambiguous QuickStart at the USBmap github.
USBmap requires python which is a problem for latest Monterey: Apple removed it. But it can be obtained in other ways. I use macports.
Hi there.
To straighten out the "lore" about port mapping ...
This just refers to the fact that since Big Sur 11.3 the XhciPortLimit quirk no longer works as intended.
In the "old days" we used to use
@RehabMan 's USBInjectAll.kext along with a direct port-limit removal patch to make all available motherboard ports visible for configuring. With this to hand we then selected our 15x ports and wrote a configuration file to implement this at boot.
Truth is you
can use other methods to create a configuration map. If you have XML editing skills and understanding of it, you can simply decompile the relevant DSDT SSDT segment and edit it to match the ports you need, then "merge" it back into the main DSDT at boot. That is the purest way to achieve the results we want. (A guide exists for this written by one of the site owners).
Most people though have relied on a "helper". USBInjectAll and an SSDT-UIAC.aml configuration file was the most common method for many years. BUT it relies on being able to "see" all the motherboard ports. Hence the need for either a port-limit patch or more recently the XhciPortLimit quirk to achieve this.
The reason people often state that you should create your map while booted into Catalina is simply because at that point
both methods were working.
