Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BrcmPatchRAM2 fails when in Clover/kexts #11

Closed
RehabMan opened this issue Nov 1, 2015 · 1 comment
Closed

BrcmPatchRAM2 fails when in Clover/kexts #11

RehabMan opened this issue Nov 1, 2015 · 1 comment

Comments

@RehabMan
Copy link
Owner

RehabMan commented Nov 1, 2015

I don't use it from Clover/kexts, but...

This is the situation:

  • BrcmPatchRAM2 loads (along with BrcmFirmwareData) via injection at boot
  • it loads firmware, all is fine... probe/exit
  • because BrcmPatchRAM2 is not resident (unlike BrcmPatchRAM.kext), the kernel will eventually unload it
  • now sleep happens, then wake
  • firmware needs to be loaded.
  • the IOKit personality is present in the io catalog, but the kext is gone from memory
  • the kernel tries to load it, but guess what... it can't find it (it doesn't know to look on EFI partition!)

Result: failure of BT on wake

This results from the separation of BrcmFirmwareStore from BrcmPatchRAM2 objects. When they were one kext, BrcmFirmwareStore would keep BrcmPatchRAM2 loaded.

The fix would be to have a small object staying resident in BrcmPatchRAM2.kext (under IOResource). That way the kext will stay loaded and will be available upon wake from sleep.

@RehabMan
Copy link
Owner Author

RehabMan commented Nov 2, 2015

Fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant