All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Romain Porte <romain.porte@nokia.com>
Cc: linux-i2c@vger.kernel.org, jdelvare@suse.de
Subject: Re: Patch proposal for risky i2c addresses in i2c-tools
Date: Fri, 26 Jan 2018 19:03:30 +0100	[thread overview]
Message-ID: <20180126180330.3ep65ongfdgffbmu@ninjato> (raw)
In-Reply-To: <20180105150248.3170-1-romain.porte@nokia.com>

[-- Attachment #1: Type: text/plain, Size: 847 bytes --]

Hi Romain,

> This patchset proposes a new option for risky i2c addresses between 0x78
> and 0x7f that are currently disabled. This behavior is marked as not
> recommended, but is sometimes needed if you have a device using an
> address in this range.

Yes, meanwhile I also have a board using addresses 0x7c and 0x7f.

> It was inspired by an email from Wolfram Sang [1] that encouraged to add
> this option for using i2c-tools with devices using this address range.

This handles only part of the risky addresses. I once worked on a device
having an EEPROM using 32(!) addresses in the range from 0x00(!!)-0x1f.
And yes, because it was the only device on the bus, that actually worked.

So, the lower boundary should also be removed IMO.

And I'd much prefer a flag like 'R' which represents 'risky' better.

Thanks for doing this!

   Wolfram


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2018-01-26 18:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-05 15:02 Patch proposal for risky i2c addresses in i2c-tools Romain Porte
2018-01-05 15:02 ` [PATCH 1/3] Add risky_addr option for i2c tools Romain Porte
2018-01-05 15:02 ` [PATCH 2/3] Update help message for risky_addr option Romain Porte
2018-01-05 15:02 ` [PATCH 3/3] Update man pages for risky_addr Romain Porte
2018-01-26 18:03 ` Wolfram Sang [this message]
2018-01-29 12:26   ` Patch proposal for risky i2c addresses in i2c-tools Romain Porte
2018-01-29 13:39     ` Peter Rosin
2018-01-29 12:40 ` New patchset for risky addr, with lower bound support Romain Porte
2018-01-29 12:40   ` [PATCH v2 1/3] Add risky_addr option for i2c tools Romain Porte
2018-01-29 12:40   ` [PATCH v2 2/3] Update help message for risky_addr option Romain Porte
2018-01-29 13:45     ` Peter Rosin
2018-01-29 12:40   ` [PATCH v2 3/3] Update man pages for risky_addr Romain Porte
2018-01-29 13:57 ` Patch proposal for risky addr, with updated help messages Romain Porte
2018-01-29 13:57   ` [PATCH v3 1/3] Add risky_addr option for i2c tools Romain Porte
2018-01-29 13:57   ` [PATCH v3 2/3] Update help message for risky_addr option Romain Porte
2018-01-29 13:57   ` [PATCH v3 3/3] Update man pages for risky_addr Romain Porte
2018-02-02 12:45 ` Patch proposal for using all addresses in i2c-tools Romain Porte
2018-02-02 12:45   ` [PATCH v4 1/3] Add all_addrs option for i2c tools Romain Porte
2018-02-02 12:45   ` [PATCH v4 2/3] Update help message for all_addrs option Romain Porte
2018-02-02 12:45   ` [PATCH v4 3/3] Update man pages for all_addrs Romain Porte

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180126180330.3ep65ongfdgffbmu@ninjato \
    --to=wsa@the-dreams.de \
    --cc=jdelvare@suse.de \
    --cc=linux-i2c@vger.kernel.org \
    --cc=romain.porte@nokia.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.