4 ms·
It's phrased like that because it doesn't work on Linux and Intel refuses to document what has to be done in the kernel to make it work. As such it's hard to bl
by izacus 11y ago
It's phrased like that because it doesn't work on Linux and Intel refuses to document what has to be done in the kernel to make it work. As such it's hard to blame Linux kernel developers for not knowing how to magically poke the complex SoC into low power submission without Intel's cooperation.
- digi_owl 11y agoSadly that is usually what happens. Something or other do not work in Linux but work in Windows with OEM drivers installed? Blame Linux even though Windows is getting help from the OEM that Linux lacks...
- therein 11y agoTo be fair, Microsoft seems to be having problems putting the chip into deep sleep as well so clearly Intel is being too secretive this time. Maybe they are trying to cover something up about Skylake? I've heard from friends in OSG that they can't get the power consumption of the chip down to what Intel claims it should be in deep sleep.
- digi_owl 11y agoThanks for the heads up. Between that and the discussion elsewhere about designing with the intent of parts being "off" much of the time reminds me that Intel tried to replace TDP with another term that was supposed to take "typical" usage into account. Never mind that they recently abandonded their tick tock development strategy recently. Really starts to look like they have run into something troublesome...