From mboxrd@z Thu Jan 1 00:00:00 1970 From: Date: Fri, 15 Aug 2008 18:38:09 +0000 Subject: [lm-sensors] Single Sensor Check Message-Id: <06d401c8ff06$1103d690$330b83b0$@com> MIME-Version: 1 Content-Type: multipart/mixed; boundary="===============1056881945642736168==" List-Id: To: lm-sensors@vger.kernel.org This is a multipart message in MIME format. --===============1056881945642736168== Content-Type: multipart/alternative; boundary="----=_NextPart_000_06D5_01C8FEE4.89F23690" Content-Language: en-us This is a multipart message in MIME format. ------=_NextPart_000_06D5_01C8FEE4.89F23690 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hello, all! I need to add a check for an alarm to a single sensor in my C program, and I'd like to do so without the overhead of calling out to an external program and parsing its output (plus all the error-checking, etc.). I have been having some issues compiling lm-sensors (so that I can step through with a debugger), so perhaps you can help me short-circuit this process a little: Is there a way to read the value of a sensor (all it throws is ALARM or nothing) from somewhere (e.g. in a protected area of memory)? For example, dmidecode finds an SMBIOS table at a particular memory location, copies it, and just navigates the table to find the values for the DMI info... Are sensors accessible in a similar manner? Thanks! -Ken ------=_NextPart_000_06D5_01C8FEE4.89F23690 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello, all! I need to add a = check for an alarm to a single sensor in my C program, and I'd like to do so without = the overhead of calling out to an external program and parsing its output = (plus all the error-checking, etc.). I have been having some issues compiling = lm-sensors (so that I can step through with a debugger), so perhaps you can help me short-circuit this process a little:

Is there a way to read the value of = a sensor (all it throws is ALARM or nothing) from somewhere (e.g. in a = protected area of memory)? For example, dmidecode finds an SMBIOS table at a = particular memory location, copies it, and just navigates the table to find the = values for the DMI info... Are sensors accessible in a similar = manner?

Thanks!

-Ken

------=_NextPart_000_06D5_01C8FEE4.89F23690-- --===============1056881945642736168== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ lm-sensors mailing list lm-sensors@lm-sensors.org http://lists.lm-sensors.org/mailman/listinfo/lm-sensors --===============1056881945642736168==--