Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 11 additions & 11 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,14 +1,14 @@
###BrcmPatchRAM -- RehabMan fork
### BrcmPatchRAM -- RehabMan fork

For the most part this fork is kept in sync with the-darkvoid's verson. We are working together to improve the project.


###RehabMan Fork Downloads
### RehabMan Fork Downloads

Builds are available on bitbucket: https://bitbucket.org/RehabMan/os-x-brcmpatchram/downloads/


###Installation
### Installation

Install one of BrcmPatchRAM.kext or BrcmPatchRAM2.kext depending on OS X version, never both.

Expand All @@ -31,7 +31,7 @@ Also, if you have a non-PatchRAM device (or you're not sure), install one of Brc
* BrcmNonPatchRAM2.kext: for 10.11 or later.


###BrcmPatchRAM
### BrcmPatchRAM

__Note if you have an Apple MacBook/iMac/Mac Pro etc, follow the [Mac instructions](https://github.com/RehabMan/OS-X-BrcmPatchRAM/blob/master/README-Mac.md)__

Expand All @@ -50,7 +50,7 @@ The firmware applied is extracted from the Windows drivers and the functionality
Note that the original Apple Broadcom bluetooth devices are not RAMUSB devices, and thus do not have the same firmware mechanism.


###BrcmBluetoothInjector.kext
### BrcmBluetoothInjector.kext

To be used for OS X 10.11 or newer.

Expand All @@ -61,7 +61,7 @@ Do not use any of the other kexts (BrcmPatchRAM, BrcmPatchRAM2, BrcmFirmwareRepo
This kext is not provided in the distribution ZIP. You can build it if you wish to try it. It was removed as it presense was causing confusion for those that don't read carefully and didn't install the preferred kexts correctly. It is not currently being updated with new devices. If yours is not present, edit the Info.plist as needed.


####Supported Devices
#### Supported Devices

BrcmPatchRAM supports any Broadcom USB bluetooth device based on the BCM20702 chipset (possibly other chipsets are supported also, but this has not been tested).

Expand Down Expand Up @@ -112,7 +112,7 @@ Tested PatchRAM devices:
All of the firmwares from the Windows package are present in the kext and automatically associated with their vendor/device-ids. They are expected to work, but have not been confirmed. If you can confirm a working device not listed above, please notify via the "issues" database on github.


####More Installation Details
#### More Installation Details

BrcmPatchRAM.kext and BrcmPatchRAM2.kext can be installed either through Clover kext injection or placed in /System/Library/Extensions.
Install only one, not both, depending on system version.
Expand All @@ -125,7 +125,7 @@ You can also use a device specific firmware injector (in conjunction with BrcmFi
You will find device specfic injectors in the 'firmwares' directory of the git repository. They are not included in the distribution ZIP.


####Details
#### Details

BrcmPatchRAM consists of 2 parts:

Expand Down Expand Up @@ -177,7 +177,7 @@ The patch for 10.11 is:
```


####Troubleshooting
#### Troubleshooting

After installing BrcmPatchRAM, even though your Bluetooth icon may show up, it could be that the firmware has not been properly updated.

Expand All @@ -201,7 +201,7 @@ In order to report an error log an issue on github with the following informatio
* Dump of BrcmPatchRAM debug output from /var/log/system.log showing the firmware upload failure


####Firmware Compatibility
#### Firmware Compatibility

Some USB devices are very firmware specific and trying to upload any other firmware for the same chipset into them will fail.

Expand All @@ -221,7 +221,7 @@ The errors in between mean the firmware was not uploaded successfully, and the d
For other devices the newest firmware available (even though not specified specifically in the Windows drivers) works fine.


####New devices
#### New devices

In order to support a new device, the firmware for the device needs to be extracted from existing Windows drivers.

Expand Down