Could you include the firmware for supported BCM inside kext? For example, now I cannot use this kext for "fresh install" MacOS from recovery image, as I have to put firmware to MacOS filesystem (e.g. /usr/local/share/firmware/wifi) and have to retreive Device Path (e.g. PciRoot(0x0)/...) with some MacOS tools, such as HackingTool. If I have no MacOS installed, I cannot put the firmware to MacOS filesystem and cannot retreive the DevicePath, so there is no Wi-Fi, when I try to boot from Recovery image. Alternatively, the firmware can be located at the kext folder and the path to this folder might be configured anythere (if it is really necessary) or it might be used the fixed name for the firmware in the kext folder.
Could you include the firmware for supported BCM inside kext? For example, now I cannot use this kext for "fresh install" MacOS from recovery image, as I have to put firmware to MacOS filesystem (e.g. /usr/local/share/firmware/wifi) and have to retreive Device Path (e.g. PciRoot(0x0)/...) with some MacOS tools, such as HackingTool. If I have no MacOS installed, I cannot put the firmware to MacOS filesystem and cannot retreive the DevicePath, so there is no Wi-Fi, when I try to boot from Recovery image. Alternatively, the firmware can be located at the kext folder and the path to this folder might be configured anythere (if it is really necessary) or it might be used the fixed name for the firmware in the kext folder.