- Joined
- Mar 6, 2012
- Messages
- 185
- Motherboard
- 15ZD960-GX3DK
- CPU
- i3-6100U
- Graphics
- HD 520
- Mobile Phone
Good find.
OK... so maybe no bug here. I missed seeing the HWPEnable option.
The HWP option has always enabled CpuPm/PluginType inject.
In that case, we are seeing the correct behavior. Because Generate/PluginType is unspecified, but HWPEnable is specified, we should expect CpuPm/PluginType SSDT inject.
But if setting Generate/PluginType=false does not avoid the CpuPm/PluginType=1 inject, then we have another bug that should be fixed (because then you'd be able to use HWPEnable and avoid CpuPM table with Generate/PluginType=false).
Personally, I don't use HWPEnable as it is never needed.... HWP is enabled by simply using an HWP enabled SMBIOS. No Clover features needed for that.
Backward compatibility sucks.
But if setting Generate/PluginType=false does not avoid the CpuPm/PluginType=1 inject, then we have another bug that should be fixed (because then you'd be able to use HWPEnable and avoid CpuPM table with Generate/PluginType=false).
-> i confirmed this part on my sandy and skylake by using each options.
right. i also never use hwpenable option. i'm always use vector frequency's hwp option for laptop. actually we don't need hwpenable option in config.plist. always depended on vector data for boot/sleep's hwp.
i will remove that line to avoid confusion. thank you so much.