linux-kernel - Enigma of Hardware Monitoring in 2.6.20.x or 2.6.21

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 27 Apr 2007 20:15:16 +0530
From:	"Sunil Naidu" <akula2.shark@...il.com>
To:	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Enigma of Hardware Monitoring in 2.6.20.x or 2.6.21

Hello,

I am did compile those kernels to the best available hardware in a
P-III machine. (Research experiment - P-III box is a part of Wireless
stuff).

I have this enigma called Hardware Monitoring support on many boards. Because:

a) Vendors don't give enough info - which chips are meant for Hardware
Monitoring in a particular board, say in this case a P-III 810E or P4
945 or Core2Duo 965/975 boards.
b) Unfortunately, there isn't any reference available in the Config to
select the chips for the respective boards. Example - for 810E - some
x chip is to be enabled in that tree.

How to solve this problem? How to know in Linux (any commands) whether
H/W Mon is supported by 810E board or 945 board? (apart from digging
from the manuals to narrow down the problem).

I am willing to do something for this task (volunteer). Comments?

~Akula2
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/