Aleksander

Hi lads. I've managed to make it work. I've got a 1028:0023 one. She worked fine in Linux but when I tried to boot macOS, it either hanged or caused reboot. When I masked pins as Naidis did, macOS started to boot and see the device. Actually she works with both AirPortBrcm4360 and AirPortBrcmNIC but requires AirportBrcmFixup to pass some Apple's checks. There's my config: <key>PciRoot(0x0)/Pci(0x1c,0x07)/Pci(0x0,0x0)</key> <dict> <key>compatible</key> <string>pci14e4,4353</string> <key>AAPL,slot-name</key> <string>Built In</string> <key>name</key> <string>pci14e4,43a3</string> <key>IOName</key> <string>pci14e4,43a3</string> <key>model</key> <string>Apple Wifi Card</string> <key>device_type</key> <string>AirPort</string> </dict> where Pci(0x1c,0x07) is an IO address, there's Hervé's post about finding thereof. The "compatible" key make it work with AirPortBrcm4360 too. So brcmfx-driver=1 and brcmfx-driver=2 work and you can don't use that boot arg at all. As for Bluetooth, it seems that the actual problem is that the original BrcmPatchRAM2 uses zipped firmware and it fails. When I tried raw hex, it worked. But I don't keep anything in L/E or S/L/E, my partition is a vanilla macOS. Everything custom is in the EFI partition. So I took 3 versions of the firmware: BCM4350C5_003.006.007.0095.1703_v5799 BCM4350C5_003.006.007.0145.2724_v6820 BCM4350C5_003.006.007.0221.4688_v8784 put them into "firmwares" dir of the repo, changed in the script zhx to hex and generated the C++ file with the firmwares. I compiled against 10.14 BrcmFirmwareData and BrcmPatchRAM2 (the second isn't necessary, just for a good measure). In BrcmPatchRAM2's plist I removed everything except 0a5c_6412 since it's the matter in hand. And now everything works from clover/kexts. If you're going to try it, there's one precaution. It's better to remove and pair again an audio device after loading a new firmware. brcm_kexts.tar.gz