ric96 wrote:WHY the hell do they have force_turbo=1 enabled??? AFAIK enabling this instantly voids your warranty!

Code: Select all
force_turbo
Disables dynamic cpufreq driver and minimum settings below. Enables H.264/V3D/ISP overclock options. Default 0. May set warranty bitThnx.ricl wrote:http://elinux.org/RPiconfig#force_turbo_mode
I believe that the 'may' does not apply to the Pi B 2. The other two lines in 10586 config.txt just force 900Mhz with no scaling.Code: Select all
force_turbo Disables dynamic cpufreq driver and minimum settings below. Enables H.264/V3D/ISP overclock options. Default 0. May set warranty bit

Lol, brilliant. What were the reasons?ric96 wrote:Until about 6 months ago i uses to think the "warranty bit" was actually a physical material (like a tiny tape or paste) under the soc that would change color if the cpu was to go beyond 85c.
I had my reasons to belive that.
1) i was unaware of an on board rom in the SoCShiftPlusOne wrote:Lol, brilliant. What were the reasons?ric96 wrote:Until about 6 months ago i uses to think the "warranty bit" was actually a physical material (like a tiny tape or paste) under the soc that would change color if the cpu was to go beyond 85c.
I had my reasons to belive that.
I think it can be read from the JTAG port which does not require a booted system however it is not very likely that any of the vendors would take the time to set up the equipment to do so.ric96 wrote: 3) if the SoC was unusable how would they check the warranty status?
Yup, i once did let the magic smoke escape from by Brev2.fruit-uk wrote:They can tell where the magic smoke got out