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-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 05 May 2014 10:46:23 -0700
From:	Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>
To:	Guenter Roeck <linux@...ck-us.net>
CC:	Linux Kernel <linux-kernel@...r.kernel.org>,
	"Yu, Fenghua" <fenghua.yu@...el.com>,
	"lm-sensors@...sensors.org" <lm-sensors@...sensors.org>
Subject: Re: coretemp.0 folder contents changed

On 05/05/2014 10:32 AM, Guenter Roeck wrote:
> On Mon, May 05, 2014 at 10:13:11AM -0700, Srinivas Pandruvada wrote:
>> Hi,
>>
>> for kernel : 3.15.rc3 .
>>
>> Is there any change in the coretemp? Previously we used to see,
>> tempx data (like temp2_input, temp2_max etc.)
>> /sys/devices/platform/coretemp.0/.
>>
> That isn't where you are supposed to look for hwmon attributes.
>
>> Now We don't see them. Now we have to go
>> /sys/devices/platform/coretemp.0/hwmon/hwmon?/ to get these values.
>>
> This is also not the correct location.
>
> You should be looking in /sys/class/hwmon/hwmonX/.
>
> There will be a name attribute either in /sys/class/hwmon/hwmonX/name
> or in /sys/class/hwmon/hwmonX/device/name. For coretemp, the value
> reported in the name attribute will be 'coretemp'. This defines the
> directory where the actual sensor attributes will be located.
>
> A better approach might be to use libsensors instead of directly
> accessing attributes.
>
> To give you the background, hwmon attributes are in the process of
> being moved from the parent device to the hwmon device, or from
> /sys/class/hwmon/hwmonX/device/ to /sys/class/hwmon/hwmonX/,
> as part of an effort to streamline the code and make it more
> consistent and maintainable.
>
> Guenter
>
Thanks for your quick reply.

-Srinivas
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ