Editing Overclocking
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
- | == | + | ==Overclocking== |
+ | |||
+ | This page is about overclocking the [[Nokia N900|N900]]. For the N8x0 see [http://talk.maemo.org/showthread.php?t=12464 this thread on talk.maemo.org] | ||
- | + | # ''WORK IN PROGRESS, HELP IF YOU WANT'' | |
Overclocking is discussed in [http://talk.maemo.org/showthread.php?t=39753 this thread]. Benchmark results can be found [http://talk.maemo.org/showthread.php?p=605189 here]. If you're more interested in power saving read [http://talk.maemo.org/showthread.php?t=49654 this]. | Overclocking is discussed in [http://talk.maemo.org/showthread.php?t=39753 this thread]. Benchmark results can be found [http://talk.maemo.org/showthread.php?p=605189 here]. If you're more interested in power saving read [http://talk.maemo.org/showthread.php?t=49654 this]. | ||
- | + | The [[Kernel_Power]] article includes [[Kernel_Power#Basic.2C_Conservative_Undervolting.2Foverclocking|instructions on overclocking with ''kernel-config'']]. You might save yourself time by trying that first. | |
==Warnings== | ==Warnings== | ||
* Overclocking WILL VOID YOUR WARRANTY. Your warranty does not cover running the device beyond the specifications. | * Overclocking WILL VOID YOUR WARRANTY. Your warranty does not cover running the device beyond the specifications. | ||
- | * The lifetime of your device WILL get reduced | + | * The lifetime of your device WILL get reduced (see below) |
- | * Your | + | * Your data might get corrupted (for example, file system corruption) |
- | * | + | * Every device is an individual, what is stable for others might not be for you |
+ | * If you encounter ANY unusual problems, lower your clock frequency (though it might be too late then, see [[:wikipedia:Electromigration]]) | ||
* You do it at your own responsibility. No whining afterwards. If you're unsure, don't do it. | * You do it at your own responsibility. No whining afterwards. If you're unsure, don't do it. | ||
- | * Nokia's overclocking warning: 500 MHz is the normal frequency. Everything above is not good for your device, even with the stock kernel. | + | * [http://depot.javispedro.com/nit/thewarningtm.jpeg Nokia's overclocking warning]: 500 MHz is the normal frequency. Everything above is not good for your device, even with the stock kernel. |
* Igor Stoppa's [http://talk.maemo.org/showpost.php?p=596149&postcount=904 warning] and [http://talk.maemo.org/showpost.php?p=603833&postcount=66 comment] | * Igor Stoppa's [http://talk.maemo.org/showpost.php?p=596149&postcount=904 warning] and [http://talk.maemo.org/showpost.php?p=603833&postcount=66 comment] | ||
* [http://talk.maemo.org/showpost.php?p=596274&postcount=937 chip vendors specs] | * [http://talk.maemo.org/showpost.php?p=596274&postcount=937 chip vendors specs] | ||
Line 23: | Line 26: | ||
* It is usually much longer (several years) than the warranty period, so that even with heavy use within the specifications it would not fail before warranty ends. | * It is usually much longer (several years) than the warranty period, so that even with heavy use within the specifications it would not fail before warranty ends. | ||
* With overclocking users may see considerable speed improvements and lower latency in user experience which could extend the actual lifetime (of being used) as the device could keep up with the newer models. | * With overclocking users may see considerable speed improvements and lower latency in user experience which could extend the actual lifetime (of being used) as the device could keep up with the newer models. | ||
- | * | + | * Naive overclocking with stock voltages is definitely bad for most components in your device, especially if the device is continuously locked at high frequencies with high load (see TI specs). |
* Specifications give guarantees for the worst-case scenarios that are covered by the warranty. The best-case scenario may be different for every device but is not covered by warranty. | * Specifications give guarantees for the worst-case scenarios that are covered by the warranty. The best-case scenario may be different for every device but is not covered by warranty. | ||
* However, there is an open debate whether '''mild''' (<40%) overclocking with lower voltages (undervolting) does actually harm or is even less harmful than the stock settings. See [[#Undervolting and voltage tables]] for an explanation why undervolting in fact won't help anything due to chip using SmartReflex Technology (which can not be disabled). | * However, there is an open debate whether '''mild''' (<40%) overclocking with lower voltages (undervolting) does actually harm or is even less harmful than the stock settings. See [[#Undervolting and voltage tables]] for an explanation why undervolting in fact won't help anything due to chip using SmartReflex Technology (which can not be disabled). | ||
Line 31: | Line 34: | ||
==Overclocking, bugzilla & errors== | ==Overclocking, bugzilla & errors== | ||
- | * Running a device overclocked for long periods of time could produce unwanted side effects, even persisting ones that won't revert when overclocking is stopped. If you are experiencing errors following | + | * Running a device overclocked for long periods of time could produce unwanted side effects, even persisting ones that won't revert when overclocking is stopped. If you are experiencing errors following Overclocking and intend to report those errors to talk.maemo.org or bugzilla, please consider the following : |
** Errors induced by overclocking will not always appear to be as such. | ** Errors induced by overclocking will not always appear to be as such. | ||
** It will be considered a good idea to reproduce your error / problem on a device which has never been overclocked AT ALL, before proceeding with actions regarding your problem. | ** It will be considered a good idea to reproduce your error / problem on a device which has never been overclocked AT ALL, before proceeding with actions regarding your problem. | ||
Line 37: | Line 40: | ||
* The reason for these requirements is that there are many problems pending for developer's attention. It is a huge waste of time to try and trace down an error without knowing all the facts, just to find out in the end that the particular problem was caused by a damaged hardware. If the developers know about it, they can take it into account and won't rule out a 1+1=3 problem on the reporter's device during their analysis. | * The reason for these requirements is that there are many problems pending for developer's attention. It is a huge waste of time to try and trace down an error without knowing all the facts, just to find out in the end that the particular problem was caused by a damaged hardware. If the developers know about it, they can take it into account and won't rule out a 1+1=3 problem on the reporter's device during their analysis. | ||
- | == | + | ==Available kernels== |
- | + | Overclocking requires installation of a custom kernel. There are two types of kernels: | |
- | + | # modified [[Maemo 5/PR1.1|PR1.1]] kernels by Lehto and others. The only difference from the stock Nokia kernel is the change of the available hardcoded frequencies. | |
- | + | # enhanced kernels by titan (highly recommended). They are compatible with [[Maemo 5/PR1.2|PR1.2]] and [[Maemo 5/PR1.3|PR1.3]], contain lots of additional features (IPv6, NAT etc) and bugfixes. In addition they include a large set of possible frequencies (125 MHz-1.15 GHz) which you manually set and try out without flashing a new kernel. The defaults are set to the standard 250-600 MHz range. The kernel can be installed via HAM from the [[extras-testing]] or [[extras-devel]] catalog. | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | == | + | === Jakiman's Guide to Overclocking for Newcomers === |
- | Overclocking | + | |
- | + | ||
- | + | [http://talk.maemo.org/showpost.php?p=595582&postcount=774 Jakiman's Overclock Guide / Summary] (constantly updated) | |
- | + | ||
- | + | ||
- | + | === Installation of Lehto's PR1.1 kernels === | |
- | + | [http://talk.maemo.org/showpost.php?p=594200&postcount=309 Lehto's Kernels] | |
+ | *No longer available* Sorry about that. -Lehto | ||
- | ==== | + | === Installation of titan's enhanced kernels === |
- | + | ||
- | + | ||
- | + | ||
- | + | This kernel makes it possible to dynamically change the maximum frequency up to 1.15 GHz (supported frequencies are 125, 250, 500, 550, 600, 700, 750, 805, 850, 900, 950, 1000, 1100, 1150 MHz). | |
- | + | ||
- | + | see the separate page for this kernel: [[Kernel_Power]] | |
- | + | ||
- | + | [http://talk.maemo.org/showthread.php?t=43420 talk.maemo.org: Discussion of the enhanced kernel] | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | == | + | ==Additional information and hints== |
- | + | # the frequencies available in the Nokia kernel are: 250, 500, 550 and 600 MHz. | |
+ | # the CPU does '''NOT IDLE''' at the lowest frequency (250 MHz) but it '''SLEEPS''' at 0 MHz! Thus, reducing the lowest frequency would not reduce power consumption. It is only activated during low workload and may actually consume more power than a higher frequency, as it takes more time to go back to sleep/idle state. | ||
+ | # setting the lowest frequency to 125 MHz does NOT improve battery life. In fact, many people noticed worse battery life, instability and worse responsiveness, | ||
+ | # Nokia [http://talk.maemo.org/showpost.php?p=601691&postcount=1823 locks the device to 600 MHz] during phone calls. This may be a bug. It also [http://talk.maemo.org/showpost.php?p=600721&postcount=1720 affects] Lehto's kernels. | ||
+ | # the telephone app is closed-source and broken. After a phone call it sets the maximum to 600 Mhz and the minimum to 250 MHz (or 125 MHz if available) irrespective of what you have set before. The are some workarounds in the Kernel-power kernel. | ||
+ | # when connected via USB the device locks the minimum frequency to 500 Mhz. | ||
+ | # By default the device is configured to use 125 MHz as the lowest frequency but it not enabled in the kernel [https://bugs.maemo.org/show_bug.cgi?id=7116 pmconfig bug] | ||
+ | # [http://talk.maemo.org/showpost.php?p=599870&postcount=170 improving responsiveness] | ||
+ | # [http://talk.maemo.org/showpost.php?p=599618&postcount=168 safe pmconfig configuration] | ||
+ | # the warning <pre>WARNING: at arch/arm/mach-omap2/clock34xx.c:443 omap3_noncore_dpll_set_rate+0x28c/0x2dc()</pre> in the kernel logs (dmesg) only happens if the invalid 800 MHz frequency was selected. ignore it. | ||
+ | # [http://talk.maemo.org/showpost.php?p=603585&postcount=189 saving more battery power when idle] | ||
+ | # EvilJazz had photoshopped a [http://talk.maemo.org/showpost.php?p=605523&postcount=90 picture of a device being overclocked 1.7GHz]. It's a '''prank'''! | ||
+ | # reading one of the temperature sensors "cat /sys/devices/platform/omap34xx_temp/temp1_input" | ||
- | + | ==Useful stuff== | |
- | + | ===Show current CPU frequency=== | |
- | + | awk '{print $1/1000" MHz"}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq | |
- | + | '''Important: this command may cause the CPU to bump up to its highest allowed frequency (in other words, you are likely to only see the highest frequency reported when checking this way).''' | |
- | + | ||
- | + | ||
- | + | ||
- | == | + | ===Set maximum CPU frequency=== |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | From root terminal: | |
- | + | echo "echo 600000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq" | root | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | Replace 600000 with desired maximum frequency. Pay attention to the two exceptions in titan's kernels (124999 and 599000). The list of available frequencies on your device/kernel can be obtained with command: | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | awk '{print $1/1000" MHz"}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state | |
- | === | + | ===Script for analyzing time_in_state (by rooted) - rev7=== |
- | + | ||
''I've stopped the development of this script and I hope someone will make use of the code. I hope titan includes it in "kernel-config show" or "kernel-config debug". -rooted'' | ''I've stopped the development of this script and I hope someone will make use of the code. I hope titan includes it in "kernel-config show" or "kernel-config debug". -rooted'' | ||
Line 291: | Line 169: | ||
Temperature: 31 degrees C</pre> | Temperature: 31 degrees C</pre> | ||
- | === | + | ===Analyzing time in state, including idle mode stats (by ArbitRabbit)=== |
- | + | ||
The following script will show the current frequency and statistics for each state, including time spent in idle mode when the CPU is actually sleeping. This script works with the special frequency handling in Titan's kernel. | The following script will show the current frequency and statistics for each state, including time spent in idle mode when the CPU is actually sleeping. This script works with the special frequency handling in Titan's kernel. | ||
Line 361: | Line 238: | ||
Known Bugs: Requires the Phone to be booted for an hour or so before it results in decent stats. | Known Bugs: Requires the Phone to be booted for an hour or so before it results in decent stats. | ||
- | ===Combined helper script=== | + | ===Combined helper script (by evilJazz)=== |
- | + | ||
The following script will show the current frequency and statistics. It also accepts two optional parameters that will set the max and/or min frequencies (in MHz unit). Calling the script without these parameters will not set the new clocking. Instead it will just show the current frequencies and statistics. | The following script will show the current frequency and statistics. It also accepts two optional parameters that will set the max and/or min frequencies (in MHz unit). Calling the script without these parameters will not set the new clocking. Instead it will just show the current frequencies and statistics. | ||
Line 421: | Line 297: | ||
124.999 MHz: 0.0 % ( 0)</pre> | 124.999 MHz: 0.0 % ( 0)</pre> | ||
- | ===Underclock/Overclock when phone is | + | ===Underclock/Overclock when phone is Locked/Unlocked (by Fecn)=== |
- | + | ||
When locked, the limits are changed to 250/500 Mhz to save power - I don't need my phone to be fast when it's sitting there doing nothing. (I did try with 125 Mhz as minimum but it caused an unresponsive touchscreen during incoming phone calls and alarms) | When locked, the limits are changed to 250/500 Mhz to save power - I don't need my phone to be fast when it's sitting there doing nothing. (I did try with 125 Mhz as minimum but it caused an unresponsive touchscreen during incoming phone calls and alarms) | ||
Line 496: | Line 371: | ||
kernel-config limits 250 $MAXSPEED | kernel-config limits 250 $MAXSPEED | ||
</pre> | </pre> | ||
+ | |||
+ | ==Changing the Kernel== | ||
+ | |||
+ | ===Installing a modified Kernel=== | ||
+ | |||
+ | ====Flashing using PC==== | ||
+ | |||
+ | # Power off the N900 completely. | ||
+ | # Hold "u" on the N900's keyboard, while holding, connect it to the PC via USB cable. | ||
+ | # You will see usb icon on top right of white Nokia screen. | ||
+ | # Now you can let go of "u" on the keyboard. | ||
+ | # Now use flasher utility with the kernel file located in the same directory.<pre>flasher-3.5 -k image_file_name -f -R</pre> | ||
+ | # It should take about 1-2 seconds then it'll say Done. | ||
+ | # Now your N900 will show white Nokia screen. (reboot) | ||
+ | # At this time, you can pull out the USB cable. | ||
+ | # N900 should finish booting up if all goes well. | ||
+ | # Test out your phone as usual. (Apps, browser, camera, phone etc etc) | ||
+ | # If any abnormal events occur frequently (crash, hang, screen corruption etc), turn it off, flash it to a slower kernel and test again. | ||
+ | note: For Windows7 64bit users, you may need to use WindowsXP mode. ([http://www.youtube.com/watch?v=Bx6dblXl2eo Youtube Tutorial]) | ||
+ | |||
+ | ====Flashing from N900 xterminal==== | ||
+ | |||
+ | * do a backup, have a PC nearby and know you are able to flash the N900 with flasher-3.5 - just in case | ||
+ | |||
+ | # Launch xterminal app then type sudo gainroot (need rootsh installed) | ||
+ | # Type:<pre>softupd -vv -s --local</pre>(that is a double v) | ||
+ | # Open new terminal | ||
+ | # Type:<pre>flasher --local -f -k <kernel_zimage_file_with_path></pre> | ||
+ | # You'll see the flashing (takes some time) | ||
+ | # Type "sync" to save changes | ||
+ | # Type "reboot" and enter to restart | ||
+ | # Test out your phone as usual. (Apps, browser, camera, phone etc etc) | ||
+ | # If any abnormal events occur frequently (crash, hang, screen corruption etc), turn it off, flash it to a slower kernel and test again. | ||
+ | |||
+ | '''You are fully responsible for any damage caused by overclocking. Not anyone else.''' | ||
+ | |||
+ | ===Reverting to the Original Kernel=== | ||
+ | |||
+ | If you want to revert to the original kernel, execute: | ||
+ | |||
+ | apt-get install --reinstall kernel kernel-flasher | ||
+ | |||
+ | === Fixing the version information === | ||
+ | |||
+ | If your version information got lost (control panel -> version) you can fix it by reinstalling the package that is listed with: | ||
+ | dpkg -l "mp-fremantle*" | ||
+ | for example, "mp-fremantle-generic-pr" (for some firmwares 002 or 003 instead of generic) and then execute: | ||
+ | apt-get install --reinstall mp-fremantle-generic-pr | ||
+ | |||
+ | ==Undervolting and voltage tables== | ||
+ | |||
+ | See: http://talk.maemo.org/showpost.php?p=628839&postcount=81 | ||
+ | |||
+ | Extract from the post: | ||
+ | |||
+ | <code>CPU power consumption (without constants) = leakage + capacitance + switching = voltage^2 + frequency + (voltage^2 * frequency)</code> | ||
+ | |||
+ | One factor reducing CPU lifetime is the current it is running with. | ||
+ | |||
+ | <code>CPU dynamic power consumption = capacitance * frequency * voltage^2</code> ([[:wikipedia:Dynamic_frequency_scaling]]) | ||
+ | |||
+ | As can be seen from the formula, lower voltage plays greater part in CPU consumption than frequency. By reducing the voltage the damage of overclocking can be reduced and the battery life time extended. Alas, this claim only holds true for architectures not regulating the real voltage and current in special on chip regulators, like OMAP is known to do for almost every gate in their CPU and other SoC function blocks. TI calls this feature SmartReflex™ and lowering the voltage applied to the whole SoC, like suggested here, only reduces the voltage drop across these regulators, thus no positive effect on electromigration damage ([[:wikipedia:Electromigration]]) caused by overclocking is to be expected. | ||
+ | |||
+ | ===Calculating voltages=== | ||
+ | |||
+ | According to [http://talk.maemo.org/showpost.php?p=606031&postcount=2375 this calculations] the voltage can be varied in steps of 0.0125 V with values 0-72. The formula is (with x being the kernel parameter value): | ||
+ | |||
+ | <code>V = x * 0.0125 + 0.6</code> | ||
+ | |||
+ | Examples: | ||
+ | |||
+ | Lowest voltage (x = 0): 0 * 0.0125 + 0.6 = 0 + 0.6 = 0.6 V | ||
+ | Highest voltage (x = 72): 72 * 0.0125 + 0.6 = 0.9 + 0.6 = 1.5 V | ||
+ | Random voltage (x = 38): 38 * 0.0125 + 0.6 = 0.475 + 0.6 = 1.075 V | ||
+ | |||
+ | ===Summary=== | ||
+ | |||
+ | FREQUENCY Nokia LV ULV XLV ideal | ||
+ | 0 MHz 30 30 25 30 30 | ||
+ | 125 MHz 30 30 25 20 30 | ||
+ | 250 MHz 38 38 25 30 30 | ||
+ | 500 MHz 48 48 33 33 30 | ||
+ | 550 MHz *54* 48 38 38 33 | ||
+ | 600 MHz 60 *54* 38 38 38 | ||
+ | 700 MHz 54 45 45 45 | ||
+ | 750 MHz 54 45 45 45 | ||
+ | 810 MHz 54 48 48 48 | ||
+ | 850 MHz 54 48 48 48 | ||
+ | 900 MHz 54 *54* *54* *54* | ||
+ | 950 MHz 54 54 54 54 | ||
+ | 1000 MHz 60 60 60 60 | ||
+ | 1100 MHz 72 72 72 72 | ||
+ | 1150 MHz 72 72 72 72 | ||
+ | |||
+ | Note: Asterisks indicate the first frequency in the kernel which needs overvoltage. | ||
+ | |||
+ | ===/sys/power/vdd1_opps_vsel values=== | ||
+ | |||
+ | LV: "30 30 38 48 48 54 54 54 54 54 54 54 60 72 72" | ||
+ | ULV: "25 25 25 33 38 38 45 45 48 48 54 54 60 72 72" | ||
+ | XLV: "30 20 30 33 38 38 45 45 48 48 54 54 60 72 72" | ||
+ | ideal: "30 30 30 30 33 38 45 45 48 48 54 54 60 72 72" | ||
+ | |||
+ | ===Kernels' specifications=== | ||
+ | |||
+ | ====Nokia's kernel==== | ||
+ | |||
+ | VALUE VOLTAGE FREQUENCY DYNAMIC POWER | ||
+ | 30 0.975 V 0 MHz 0.000 V²/us | ||
+ | 30 0.975 V 125 MHz 118.828 V²/us | ||
+ | 38 1.075 V 250 MHz 288.906 V²/us | ||
+ | 48 1.200 V 500 MHz 720.000 V²/us | ||
+ | 54 1.275 V 550 MHz 894.094 V²/us | ||
+ | 60 1.350 V 600 MHz 1093.500 V²/us | ||
+ | |||
+ | ====titan's LV kernel==== | ||
+ | |||
+ | VALUE VOLTAGE FREQUENCY DYNAMIC POWER | ||
+ | 30 0.975V 0 MHz 0.000 V²/us | ||
+ | 30 0.975V 125 MHz 118.828 V²/us | ||
+ | 38 1.075V 250 MHz 288.906 V²/us | ||
+ | 48 1.200V 500 MHz 720.000 V²/us | ||
+ | 48 1.200V 550 MHz 792.000 V²/us | ||
+ | 54 1.275V 600 MHz 975.375 V²/us | ||
+ | 54 1.275V 700 MHz 1137.938 V²/us | ||
+ | 54 1.275V 750 MHz 1219.219 V²/us | ||
+ | 54 1.275V 810 MHz 1316.756 V²/us | ||
+ | 54 1.275V 850 MHz 1381.781 V²/us | ||
+ | 54 1.275V 900 MHz 1463.062 V²/us | ||
+ | 54 1.275V 950 MHz 1544.344 V²/us | ||
+ | 60 1.350V 1000 MHz 1822.500 V²/us | ||
+ | 72 1.500V 1100 MHz 2475.000 V²/us | ||
+ | 72 1.500V 1200 MHz 2700.000 V²/us | ||
+ | |||
+ | ====titan's ULV kernel==== | ||
+ | |||
+ | VALUE VOLTAGE FREQUENCY DYNAMIC POWER | ||
+ | 25 0.912V 0 MHz 0.000 V²/us | ||
+ | 25 0.912V 125 MHz 103.968 V²/us | ||
+ | 25 0.912V 250 MHz 207.936 V²/us | ||
+ | 33 1.012V 500 MHz 512.072 V²/us | ||
+ | 38 1.075V 550 MHz 635.594 V²/us | ||
+ | 38 1.075V 600 MHz 693.375 V²/us | ||
+ | 45 1.163V 700 MHz 946.798 V²/us | ||
+ | 45 1.163V 750 MHz 1014.427 V²/us | ||
+ | 48 1.200V 810 MHz 1166.400 V²/us | ||
+ | 48 1.200V 850 MHz 1224.000 V²/us | ||
+ | 54 1.275V 900 MHz 1463.062 V²/us | ||
+ | 54 1.275V 950 MHz 1544.344 V²/us | ||
+ | 60 1.350V 1000 MHz 1822.500 V²/us | ||
+ | 72 1.500V 1100 MHz 2475.000 V²/us | ||
+ | 72 1.500V 1200 MHz 2700.000 V²/us | ||
+ | |||
+ | ====titan's XLV kernel==== | ||
+ | |||
+ | VALUE VOLTAGE FREQUENCY DYNAMIC POWER | ||
+ | 30 0.975V 0 MHz 0.000 V²/us | ||
+ | 20 0.850V 125 MHz 90.312 V²/us | ||
+ | 30 0.975V 250 MHz 237.656 V²/us | ||
+ | 33 1.012V 500 MHz 512.072 V²/us | ||
+ | 38 1.075V 550 MHz 635.594 V²/us | ||
+ | 38 1.075V 600 MHz 693.375 V²/us | ||
+ | 45 1.163V 700 MHz 946.798 V²/us | ||
+ | 45 1.163V 750 MHz 1014.427 V²/us | ||
+ | 48 1.200V 810 MHz 1166.400 V²/us | ||
+ | 48 1.200V 850 MHz 1224.000 V²/us | ||
+ | 54 1.275V 900 MHz 1463.062 V²/us | ||
+ | 54 1.275V 950 MHz 1544.344 V²/us | ||
+ | 60 1.350V 1000 MHz 1822.500 V²/us | ||
+ | 72 1.500V 1100 MHz 2475.000 V²/us | ||
+ | 72 1.500V 1150 MHz 2587.500 V²/us | ||
+ | |||
+ | ====titan's ideal kernel==== | ||
+ | |||
+ | VALUE VOLTAGE FREQUENCY DYNAMIC POWER | ||
+ | 30 0.975V 0 MHz 0.000 V²/us | ||
+ | 30 0.975V 125 MHz 118.828 V²/us | ||
+ | 30 0.975V 250 MHz 237.656 V²/us | ||
+ | 30 0.975V 500 MHz 475.312 V²/us | ||
+ | 33 1.012V 550 MHz 563.279 V²/us | ||
+ | 38 1.075V 600 MHz 693.375 V²/us | ||
+ | 45 1.163V 700 MHz 946.798 V²/us | ||
+ | 45 1.163V 750 MHz 1014.427 V²/us | ||
+ | 48 1.200V 810 MHz 1166.400 V²/us | ||
+ | 48 1.200V 850 MHz 1224.000 V²/us | ||
+ | 54 1.275V 900 MHz 1463.062 V²/us | ||
+ | 54 1.275V 950 MHz 1544.344 V²/us | ||
+ | 60 1.350V 1000 MHz 1822.500 V²/us | ||
+ | 72 1.500V 1100 MHz 2475.000 V²/us | ||
+ | 72 1.500V 1150 MHz 2587.500 V²/us | ||
[[Category:Power users]] | [[Category:Power users]] | ||
[[Category:N900]] | [[Category:N900]] |
Learn more about Contributing to the wiki.