Quote:
Originally Posted by qasdfdsaq
Or a design issue :P Quite a few laptops these days aren't able to run at full load continuously, often having to throttle down after a few seconds to minutes - though that's slightly different as it causes no damange.
|
Not just laptops, but pretty much all tablets and smartphones have that "issue".
Quote:
Originally Posted by qasdfdsaq
I agree with Ignition here - hardware that can't run at 100% without damaging itself is faulty.
|
I don't disagree with this. I'm saying that it's possible the software is trying to push the hardware harder than it's meant to.
Quote:
Originally Posted by qasdfdsaq
Furthermore, in practice, it actually works the opposite of how you describe at least on x86 and MIPS systems (the latter being common for routers). Most devices actually operate at 100% without being capable of throttling down or underclocking until the higher level OS is loaded. Without the OS, drivers, and CPU governors loaded, by default almost all devices will run at 100% clockspeed. Further, if something crashes during startup, it usually gets stuck at 100% forever as well.
|
I'm not going to disagree at all here, as I have limited experience with embedded devices. The ones I have dealt with do start off underclocked and spin up as hardware is initialised. In fact, it was because of this very reason that it's possible to glitch an Xbox 360 to run unsigned code. Obviously not the same thing, however.
Either way, hardware or software, enough people are having issues that Virgin needs to sort it.