Yeah. It's part of the firmware package. And the manual timing is supposed to be set in real-time after boot, or adjusted via api calls. But without implementing those api calls at the hardware layer (i.e., including the existing firmware), and making them available to the software layer via an efi extension. Or if the manufacturer simply lock the settings to a specific table at boot, etc., you can't change these settings.
So, for example - when Asus don't include these functions with their laptops (the non ROG laptops, anyway), it's done by simply not including that part of the firmware package in the "bios" flash (which consists of bios, extended acpi, nvram, etc.). The actual hardware supports it, and they use limited sets of direct api calls through various standard drivers. But the hardware layer simply lacks the software, and the timing is hard-set to a simple list at boot-time. So you can't change it, at least without attempting a bios-flash. In which case, you would of course still lack the api options to change the timing during run-time. And attempting to put a non-signed bios package on there without knowing what hardware IDs they're using and so on is.. futile.
You might wonder why they would buy expensive hardware from Intel, and not actually use the functionality they've bought. But that's just how it's done in the laptop industry in general, so don't ask questions. Or, ask questions, and be told off by support about how dumb you are that you don't understand why locking the dram to "toaster" settings, while relying on the hardware cutoff to cool the processor, is what prevents people from overclocking their laptop and destroying it.
That's just how the laptop industry works, and there's nothing you can do about it. Because reasons.
Click to expand...
Problems? See this thread at archive.org.
lappy. I have Intel XTU however the manual tuning is grayed out. Is this because my processor model does not support XTU tuning or something along the lines of a BIOS setting change? Thanks everyone!
