On 02/01/15 11:28, Richard Weinberger wrote:
> Am 01.01.2015 um 22:18 schrieb har...@ccbib.org:
>> Hi!
>>
>> On Thu, 01 Jan 2015 12:38:23 +, Jonathan Cameron
>> wrote:
>>> On 02/12/14 23:32, Richard Weinberger wrote:
Please see my current patches for your driver.
As discussed in an e
Am 01.01.2015 um 22:18 schrieb har...@ccbib.org:
> Hi!
>
> On Thu, 01 Jan 2015 12:38:23 +, Jonathan Cameron
> wrote:
>> On 02/12/14 23:32, Richard Weinberger wrote:
>>> Please see my current patches for your driver.
>>> As discussed in an earlier mail I'm testing with the DHT22 sensor only.
>
Hi!
On Thu, 01 Jan 2015 12:38:23 +, Jonathan Cameron
wrote:
> On 02/12/14 23:32, Richard Weinberger wrote:
>> Please see my current patches for your driver.
>> As discussed in an earlier mail I'm testing with the DHT22 sensor only.
>> With the IRQ changes I see 84 edges.
>>
>>
>> [PATCH 1/4
On 02/12/14 23:32, Richard Weinberger wrote:
> Please see my current patches for your driver.
> As discussed in an earlier mail I'm testing with the DHT22 sensor only.
> With the IRQ changes I see 84 edges.
>
> I have also a question on your driver. Why you increment
> DHT11_DATA_BIT_LOW/timeres b
Richard Weinberger writes:
> Harald,
>
> Am 03.12.2014 um 13:18 schrieb Harald Geyer:
> > Hi Richard,
> >
> > thanks for all the work you put into this!
> >
> > Richard Weinberger writes:
> >> Please see my current patches for your driver.
> >> As discussed in an earlier mail I'm testing with th
Harald,
Am 04.12.2014 um 14:45 schrieb Harald Geyer:
> Richard Weinberger writes:
>> 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 eff
Richard Weinberger writes:
> 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 alway
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,
> be
Harald,
Am 03.12.2014 um 13:18 schrieb Harald Geyer:
> Hi Richard,
>
> thanks for all the work you put into this!
>
> Richard Weinberger writes:
>> Please see my current patches for your driver.
>> As discussed in an earlier mail I'm testing with the DHT22 sensor only.
>> With the IRQ changes I
Am 03.12.2014 um 15:08 schrieb Harald Geyer:
> Richard Weinberger writes:
>> Harald,
>>
>> Am 03.12.2014 um 13:18 schrieb Harald Geyer:
>>> Hi Richard,
>>>
>>> thanks for all the work you put into this!
>>>
>>> Richard Weinberger writes:
I have also a question on your driver. Why you increment
Richard Weinberger writes:
> Harald,
>
> Am 03.12.2014 um 13:18 schrieb Harald Geyer:
> > Hi Richard,
> >
> > thanks for all the work you put into this!
> >
> > Richard Weinberger writes:
> >> I have also a question on your driver. Why you increment
> >> DHT11_DATA_BIT_LOW/timeres by one in the
Harald,
Am 03.12.2014 um 13:18 schrieb Harald Geyer:
> Hi Richard,
>
> thanks for all the work you put into this!
>
> Richard Weinberger writes:
>> Please see my current patches for your driver.
>> As discussed in an earlier mail I'm testing with the DHT22 sensor only.
>> With the IRQ changes I
Hi Richard,
thanks for all the work you put into this!
Richard Weinberger writes:
> Please see my current patches for your driver.
> As discussed in an earlier mail I'm testing with the DHT22 sensor only.
> With the IRQ changes I see 84 edges.
This still surprises me. With the IRQ changes I woul
13 matches
Mail list logo
