Closed driver1998 closed 4 years ago
I can patch out the check for sure, but it will be better to do the job on UEFI side.
Ok, will do.
On Tue, Jan 15, 2019 at 12:56 PM driver1998 notifications@github.com wrote:
I can patch out the check for sure, but it will be better to do the job on UEFI side.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/andreiw/RaspberryPiPkg/issues/106#issuecomment-454488393, or mute the thread https://github.com/notifications/unsubscribe-auth/AAstaxl6ZG1VQf8XfuYv3nWWxThn-r3iks5vDhZhgaJpZM4aBdqp .
-- A
I ended up added the ForceEnable DWORD in the bcmauxspi INF file anyway, so it should be fine to close this.
The current Windows bcmauxspi driver checks if SPI1 is enabled in the registers, if not, then the load fails, unless ForceEnable is set in the Windows registry. (if set, the driver enables SPI1 and continue)
bcmauxspi.cpp
And it seems currently SPI1 is not enabled by default, requiring ForceEnable=1 in the registry. Also, if you decided to add a switch to enable/disable SPI1 in the UEFI settings, remove the AUXSPI (SPI1) entry in RHPX when disabling SPI1 for rhproxy.sys to load properly. (Otherwise it will complain about required drivers are not started).