and if you wonder what linux does today without the framework; there are
mechanisms that kick in at the very end of the range, that are very
draconian like taking the 3.0Ghz processor down to effectively 100MHz,
or even a system reboot. The point of what Jacob and Srinivas are trying
to add is to intervene slightly earlier (these failsafe mechanisms are
still there) but much much more gently.
First off, we are not using the type of boards for controllers that would
burn anything up sans its normal cooling, which is entirely passive on an
atom powered board as you well know. So there is no fan to fail and start
your doomsday scenario in abut 30% of the cases now, but there are a rather
dukes mixture of other boards being used yet. Those will be replaced in
due time as they fail, or the IRQ latency finally starts costing the shop
owner money because the machine can't be run at the optimum speed with that
poorly architect-ed board, probably with Atoms or BBB's.
If you insist on doing this, in the face of ample evidence its nothing but
a feel good action on your part, then the least we ask is for a tally
signal output, far enough in advance, say 0.25 seconds, to do a graceful,
In fact, I'd go so far as to say that any hardware capable of self-
destructing in normal operation, does not need to guarded by this proposed
function, but blacklisted instead, it is patently a defective design from
square one regardless of the brand name on the box. Or just let it burn
up, the warranty returns will educate the maker/designer soon enough.