Enable asserts and make correct comment

Enable asserts for test period and correct the comments.
It is better to know why a crash happen when it could happen
than just silently die.
devices: Trivial coding style fix

* block statement doesn't need a semicolon.
* put closing curly bracket of function on a new line.

Signed-off-by: Namhyung Kim <namhyung@gmail.com>
Added a "type" field to the abstract to be used in its identification and set along with the number.
Added the "field" to reporting, so that the type and number are used from the abstract rather then hard coding the type in reporting.
Update TO-DO list while I was at it.
The previous commit wrongly replaced strings identifying abstract type to the reporting functions with a new abstract type field. This ended up braking a important Macro in the reporting that allow for the decision on whether or not to use translation or not depending on report type. This commit back out the breakage, uses the new type field in decision making for cstate cores, and adds a comment on why not to just use the field for the reporting function.
update powertop.pot
remove warnings for system call and freopn
updated active % of GPU to Powered On
configure: rework libnl detection and fix libnl-2 case (v2)

Rework libnl detection.

PKG_CHECK_MODULES macro appends FOO_CFLAGS and FOO_LIBS flags

Example:
LIBNL_CFLAGS = -I/usr/include/libnl3
LIBNL_LIBS = -lnl-genl-3 -lnl-3

while AC_SEARCH_LIBS only prepends -llibrary to LIBS, so AC_SEARCH_LIBS
is not helpful.

Use pkg-config PC file names to search for minimum package versions:
libnl 3.+ -- libnl-3.0.pc
libnl 2.+ -- libnl-2.0.pc
libnl 1.+ -- libnl-1.0.pc

Patch also changes $has_libnl_ver == 0 error message and suppresses
failed PKG_CHECK_MODULES output.

Austin pointed out that libnl-2.0 provide only libnl-2.0.pc pkg-config
file, while libnl-3 has at least 5 of them (for every `so').
This is why we check libnl-3.0.pc and libnl-genl-3.0.pc in libnl-3 case.

Many thanks to Austin Zhang for help.
v2: Namhyung Kim reported that libnl-1.0.pc on Ubuntu is named libnl-1.pc.

Reported-and-tested-by: Austin Zhang <zhang.austin@gmail.com>
Tested-by: Namhyung Kim <namhyung@gmail.com>
Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Ignore non-P-state-enabled CPUs when calculating frequency.

This fixes bogus reported CPU frequencies (actually, uninitialized
values from i965_core) when i965 monitoring is used.

Signed-off-by: Ivan Shapovalov <intelfx100@gmail.com>
transifex update
fixed issues with p-state reported CPU frequencies (actually, uninitialized
values ) extended from fix for i965 monitoring. Also found UI titles missing, so repleaced them.
cpu: Fix leftovers from the P state cpu frequency calculation

The commit 15b8bfb ("Ignore non-P-state-enabled CPUs when calculating
frequency") and 29f42b5 ("fixed issues with p-state reported CPU
frequencies") fixed frequency calculation for cpu packages but missed
it for cpu cores.  Add it.

This fixes wrong frequency report on my quad-core box: 2072.5% -> 100.0%

Cc: Ivan Shapovalov <intelfx100@gmail.com>
Signed-off-by: Namhyung Kim <namhyung@gmail.com>
up version for v2.2 release
Merge git://github.com/fenrus75/powertop