I have an ASUS ROG MAXIMUS IX FORMULA motherboard and the kexts work for causing the on-board Qualcomm Atheros QCA61x4A to recognize my Magic Mouse. It's working on macOS High Sierra 10.13.2. I'm just reporting so that it becomes listed as tested. Before the installation the Bluetooth controller was reported as functional by macOS but it couldn't scan/pair any device.
I've just put BrcmPatchRAM2.kext and BrcmFirmwareData.kext on /EFI/CLOVER/kexts/Other because I prefer to leave these extra Hackintosh kexts apart from the OS partition if possible, but I notice that the README highlights that BrcmFirmwareRepo.kext on /System/Library/Extensions is the preferred method and it's much less memory hungry, so..., is it that much better? I have 16GB RAM and I didn't get how a simple kext can be that memory hungry to my system, or is it about the controller's memory? Is there a more detailed drawback of sticking to BrcmFirmwareData.kext since I can just put it on Clover besides BrcmPatchRAM2.kext?
I have an ASUS ROG MAXIMUS IX FORMULA motherboard and the kexts work for causing the on-board Qualcomm Atheros QCA61x4A to recognize my Magic Mouse. It's working on macOS High Sierra 10.13.2. I'm just reporting so that it becomes listed as tested. Before the installation the Bluetooth controller was reported as functional by macOS but it couldn't scan/pair any device.
I've just put
BrcmPatchRAM2.kext
andBrcmFirmwareData.kext
on/EFI/CLOVER/kexts/Other
because I prefer to leave these extra Hackintosh kexts apart from the OS partition if possible, but I notice that the README highlights thatBrcmFirmwareRepo.kext
on/System/Library/Extensions
is the preferred method and it's much less memory hungry, so..., is it that much better? I have 16GB RAM and I didn't get how a simple kext can be that memory hungry to my system, or is it about the controller's memory? Is there a more detailed drawback of sticking toBrcmFirmwareData.kext
since I can just put it on Clover besidesBrcmPatchRAM2.kext
?