-
Notifications
You must be signed in to change notification settings - Fork 281
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
[suggestion] ME disablement via removing VSCC values #80
Comments
Good catch. More info:
Source: System Tools User Guide for |
@skochinsky Doesn't it also affect the normal operation of the BIOS? |
@skochinsky Doesn't it also affect the normal operation of the BIOS?
AFAIK BIOS has its own tables for talking to flash so it should continue working.
|
VSCC table is present in the descriptor region and tells the ME (and PCH?) about Vendor Specific Component Capabilities of the flash chips supported by the system.
A birdie told me that a missing VSCC value will place the ME into recovery mode since it won't be able to write to flash without knowing if the connected part is supported.
It seems the table is located at VTBA (whose value and size are encoded in the FLUMAP1).
Clearing this table may be another "soft disable" option in addition to AltMeDisable.
The text was updated successfully, but these errors were encountered: