linux-kernel - Re: [PATCH 0/2] w1: slaves: w1_therm: Add sysfs entry for current temperature

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]

Message-ID: <20150106161205.GA2912@firebird>
Date:	Tue, 6 Jan 2015 17:12:05 +0100
From:	Mariusz Gorski <marius.gorski@...il.com>
To:	Richard Weinberger <richard.weinberger@...il.com>
Cc:	Evgeniy Polyakov <zbr@...emap.net>, David Fries <David@...es.net>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/2] w1: slaves: w1_therm: Add sysfs entry for current
 temperature

On Tue, Jan 06, 2015 at 04:01:47PM +0100, Richard Weinberger wrote:
> On Tue, Jan 6, 2015 at 3:29 PM, Mariusz Gorski <marius.gorski@...il.com> wrote:
> > DS18B20 and it's brothers are pretty popular in the RaspberryPi world
> > when it comes to temperature measurement. All tutorials on the Internet
> > use the same way of parsing the output of the w1_slave sysfs file.
> > These patches add a dedicated sysfs entry called 'temp' whose only job
> > is to output the current temperature.
> 
> And what is the benefit of this patches?

Well, instead of having to parse the output of w1_slave:

$ cat w1_slave 
4d 01 55 00 7f ff 0c 10 fd : crc=fd YES
4d 01 55 00 7f ff 0c 10 fd t=20812

the userspace program gets only the interesting information,
which usually is the current temparture:

$ cat temp 
20812

> 
> -- 
> Thanks,
> //richard
--
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/