| 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
| ||
|
Message-ID: <547F8925.3050308@nod.at> Date: Wed, 03 Dec 2014 23:05:25 +0100 From: Richard Weinberger <richard@....at> To: Harald Geyer <harald@...ib.org> CC: jic23@...nel.org, knaack.h@....de, lars@...afoo.de, pmeerw@...erw.net, sanjeev_sharma@...tor.com, linux-iio@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: iio: dht11 Updates Am 03.12.2014 um 15:08 schrieb Harald Geyer: >> I was asking because I see the "dht11: WARNING: decoding ambiguous" >> very often. (with and without my patches) > > Yes, your patches shouldn't have any effect on this. > "very often" in the sense of "not always"? This would be very surprising, > because this would involve variable length clock ticks, i think. > > I guess we should include timeres into the warning message. > > Also I guess now is the time to think about a smarter decoder. Another question. Your driver defines: #define DHT11_DATA_BIT_LOW 27000 #define DHT11_DATA_BIT_HIGH 70000 If I read the manual [0] correctly these constants are T_h0/1. Why did you use 27000 for T_h0? Setting it to 26000 (the typical value as stated by the manual), I get the "decoding ambiguous" warning *always*. Setting it higher makes the message go away. Thanks, //richard [0] http://meteobox.tk/files/AM2302.pdf -- 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