On Wed, Oct 01, 2014 at 10:40:41AM -0700, Alexandru M Stan wrote:
> i2cdetect -q was broken (everything was a false positive, and no transfers
> were
> actually being sent over i2c). The way it works is by sending a 0 length write
> request and checking for NACK. This patch fixes the 0 length
> Reviewed-By: Max Schwarz
> Tested-By: Max Schwarz
Checkpatch says:
WARNING: 'Tested-by:' is the preferred signature form
Same 'Reviewed-by:'
signature.asc
Description: Digital signature
Hi Alexandru,
On Wednesday 01 October 2014 at 10:40:41, Alexandru M Stan wrote:
> i2cdetect -q was broken (everything was a false positive, and no transfers
> were actually being sent over i2c). The way it works is by sending a 0
> length write request and checking for NACK. This patch fixes the
Reviewed-By: Max Schwarz max.schw...@online.de
Tested-By: Max Schwarz max.schw...@online.de
Checkpatch says:
WARNING: 'Tested-by:' is the preferred signature form
Same 'Reviewed-by:'
signature.asc
Description: Digital signature
On Wed, Oct 01, 2014 at 10:40:41AM -0700, Alexandru M Stan wrote:
i2cdetect -q was broken (everything was a false positive, and no transfers
were
actually being sent over i2c). The way it works is by sending a 0 length write
request and checking for NACK. This patch fixes the 0 length writes
Hi Alexandru,
On Wednesday 01 October 2014 at 10:40:41, Alexandru M Stan wrote:
i2cdetect -q was broken (everything was a false positive, and no transfers
were actually being sent over i2c). The way it works is by sending a 0
length write request and checking for NACK. This patch fixes the 0
Alex,
On Wed, Oct 1, 2014 at 10:40 AM, Alexandru M Stan wrote:
> i2cdetect -q was broken (everything was a false positive, and no transfers
> were
> actually being sent over i2c). The way it works is by sending a 0 length write
> request and checking for NACK. This patch fixes the 0 length
i2cdetect -q was broken (everything was a false positive, and no transfers were
actually being sent over i2c). The way it works is by sending a 0 length write
request and checking for NACK. This patch fixes the 0 length writes and actually
sends them.
Reported-by: Doug Anderson
Signed-off-by:
i2cdetect -q was broken (everything was a false positive, and no transfers were
actually being sent over i2c). The way it works is by sending a 0 length write
request and checking for NACK. This patch fixes the 0 length writes and actually
sends them.
Reported-by: Doug Anderson
Alex,
On Wed, Oct 1, 2014 at 10:40 AM, Alexandru M Stan ams...@chromium.org wrote:
i2cdetect -q was broken (everything was a false positive, and no transfers
were
actually being sent over i2c). The way it works is by sending a 0 length write
request and checking for NACK. This patch fixes
10 matches
Mail list logo