Well, as long as we have to deal with UEFI and PSP as blackboxes anyway, this blob on top doesn't make things worse imho.
Announcement
Collapse
No announcement yet.
AMD Prepares PMF Linux Driver For "Smart PC Solutions Builder"
Collapse
X
-
Originally posted by bridgman View PostWould you be OK with a mechanism that lets you say "I am taking responsibility for fine-grained power management and do not expect warranty coverage if something goes wrong" then records the answer permanently in the hardware ? My impression from customer support is that the general answer seems to be "no". The problem is not individual developers experimenting with PM software and letting the smoke out, but thousands or millions of users running power management software written by someone they never met.
Comment
-
Originally posted by timofonic View Post
I fully agree!
But Microsoft is a platinum Linux Foundation sponsor these days. Money corrupts everything
They merged the Trojan's Horse with 6.1 kernel.
https://www.phoronix.com/news/x86-Platform-Drivers-6.1
Comment
-
Originally posted by EphemeralEft View PostI might also fail to follow proper appliance safety practices, start a kitchen fire, and then demand the company that built the appliance I destroyed replaces it at no extra cost. Wouldn't it be better to build every appliance with a camera that turns it off if it detects you trying to prepare ingredients that the company hasn't manually approved? The problem is not individual chefs experimenting with food preparation, but thousands or millions of users following cooking guides written by someone they never met.Test signature
- Likes 2
Comment
-
Originally posted by bridgman View PostThese days it's a different story, particularly in mobile products. GPUs (and presumably CPUs) can use much (MUCH) more power that the cooling system can dissipate - even getting heat out of the package is a problem - so getting best performance while not letting the smoke out is much more complicated and multi-dimensional. Even thermal limiting with dozens of sensors is too slow to avoid local meltdowns, so power management also uses distributed current sensors to anticipate thermal rise and start limiting clocks & voltages.
The key question is who takes responsibility for not letting the smoke out and killing the system. With desktop systems the worst case on the CPU side is usually that you blow up a socketed CPU, but with mobile systems the cost of damage is usually much higher, typically over 50% of the system cost. Right now HW vendors keep fine-grained power management under their control and if something goes wrong they can be pretty sure it was "their fault" rather than something the user did. There are grey areas like dust buildup in cooling solutions but that tends to happen sufficiently slowly that the firmware can adapt to it and still keep the smoke in.
That part could be implemented in hardware (for example send cores that reach 100°C to sleep till they reach 80°C) and the rest could be done with open source firmware and who ever thinkers with it has in the worst case a slow CPU. Anyone else could just use the AMD provided firmware and get AMDs intended performance.
If you overclock your CPU it can still be roasted and AMD explicitly supports overclocking (and voids warranty if it's legal in your country), so where is the problem here?
- Likes 1
Comment
-
Originally posted by bridgman View Post
I don't think the analogy works - there's a big difference between "burning what you are cooking" and "killing the stove".
Comment
-
Originally posted by Anux View PostI don't see how this is a valid reason for a closed source solution. You can basically run any modern CPU without any cooler and it will run (slow like shit of course) because it will send cores to sleep that get too hot.
That part could be implemented in hardware (for example send cores that reach 100°C to sleep till they reach 80°C) and the rest could be done with open source firmware and who ever thinkers with it has in the worst case a slow CPU. Anyone else could just use the AMD provided firmware and get AMDs intended performance.
If you overclock your CPU it can still be roasted and AMD explicitly supports overclocking (and voids warranty if it's legal in your country), so where is the problem here?
You don't have to run PMF and if you don't, as far as I know, you get the default universally safe limits.Last edited by agd5f; 25 September 2023, 05:13 PM.
Comment
-
Originally posted by Jonjolt View Post
I wasn't even thinking of this, for anyone unaware if you have enough $$$ Intel will customize the chip for you.
- Likes 1
Comment
Comment