Installer: Add bluetooth support for Broadcom/Intel chips in Monterey #923
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
osy
reviewed
Sep 8, 2021
Installer/data/BrcmPatchRAM/BrcmBluetoothInjector.kext.MaxKernel.txt
Outdated
Show resolved
Hide resolved
Installer/data/IntelBluetoothFirmware/IntelBluetoothInjector.kext.MaxKernel.txt
Outdated
Show resolved
Hide resolved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bluetoolfixup.kext is needed in Monterey for both intel and broadcom bluetooth/wifi chips.
Meanwhile, BrcmBluetoothInjector.kext (for broadcom ) and IntelBluetoothInjector.kext (for intel) must be disabled.
reference:
In addition, I found that Bluetoolfixup.kext must be loaded after polaris22 and weg in Monterey b6.
Or you will stuck at
IOResourceMatch. (This should be a bug in bluetoolfixup to be repaired later)