On Thu, Jul 29, 2010 at 7:56 PM, Marcin Juszkiewicz
wrote:
> Dnia czwartek, 29 lipca 2010 o 13:57:21 Amit Arora napisał(a):
>> I have tested this only on my desktop. I am yet to receive an ARM based
>> board, and hence couldn't test it there. So, any kind of testing and/or
>> feedback are most wel
On Thu, Jul 29, 2010 at 6:38 PM, Amit Kucheria wrote:
> On 10 Jul 29, Amit Arora wrote:
>>
>> Currently the PowerTOP tool is x86 centric and does not work on other
>> architectures, unless some changes are made.
>>
>> This patchset removes the hardcoded values for the P and C states. It does
>>
On Thu, Jul 29, 2010 at 5:42 PM, Amit Kucheria wrote:
> On 10 Jul 29, Amit Arora wrote:
>> Amit Arora (2):
>> Add OMAP3 support to PowerTOP
>> Remove hardcoded c and p states
>>
>> Makefile | 2 +-
>> cpufreqstats.c | 3 +-
>> display.c | 23 +-
>> gene
What tools and libraries should I use when writing
infrastructure-style projects? Do we have a preferred technology
list? Is there a style guide or standard templates that I can use?
This came about in writing a little web application for tracking the
changes in Linaro GCC vs upstream:
http://e
Got mine today.
I initially couldn't get a serial console on it, but it seems it's a
quite common grounding issue. Perhaps my USB serial adapter (would be
surprizing), but more likely the board. Workaround: try different
serial ports, try connecting to the board over it's mini-USB port etc.
Dnia czwartek, 29 lipca 2010 o 13:57:21 Amit Arora napisał(a):
> I have tested this only on my desktop. I am yet to receive an ARM based
> board, and hence couldn't test it there. So, any kind of testing and/or
> feedback are most welcome! Thanks!
I fetched 9f4efd1c7cc0bc9a9078fa6b83a98763a7637e2f
Dnia czwartek, 29 lipca 2010 o 13:57:21 Amit Arora napisał(a):
> I have tested this only on my desktop. I am yet to receive an ARM based
> board, and hence couldn't test it there. So, any kind of testing and/or
> feedback are most welcome! Thanks!
I fetched 9f4efd1c7cc0bc9a9078fa6b83a98763a7637e2f
On 10 Jul 29, Amit Arora wrote:
>
> Currently the PowerTOP tool is x86 centric and does not work on other
> architectures, unless some changes are made.
>
> This patchset removes the hardcoded values for the P and C states. It does
> that in two steps
> 1) Implements the OMAP3 support in PowerT
On 10 Jul 29, Amit Arora wrote:
> This patch gets the available C-states from cpuidle framework (sysfs) and
> gets the P-states information from the cpufreq (again, from sysfs). Thus it
> removes the hardcoded values for c and p states, and makes it generic enough
> to run on all the systems whi
On 10 Jul 29, Amit Arora wrote:
>
> Currently the PowerTOP tool is x86 centric and does not work on other
> architectures, unless some changes are made.
>
> This patchset removes the hardcoded values for the P and C states. It does
> that in two steps
> 1) Implements the OMAP3 support in PowerT
This patch gets the available C-states from cpuidle framework (sysfs) and gets
the P-states information from the cpufreq (again, from sysfs). Thus it removes
the hardcoded values for c and p states, and makes it generic enough to run on
all the systems which plugin to cpuidle and cpufreq kernel
This patch is based on
http://processors.wiki.ti.com/index.php/Running_PowerTOP_on_OMAP35x_platform#Updates_to_PowerTOP
Its a simple port from above location.
Signed-off-by: Amit Arora
---
Makefile |2 +-
cpufreqstats.c |2 +-
display.c | 18 ---
omapcstates.c
Currently the PowerTOP tool is x86 centric and does not work on other
architectures, unless some changes are made.
This patchset removes the hardcoded values for the P and C states. It does that
in two steps
1) Implements the OMAP3 support in PowerTOP.
2) Makes the code generic enough for all b
13 matches
Mail list logo
