Hi Wolfram, Thanks for your work. On 2019-03-11 23:33:33 +0100, Wolfram Sang wrote: > For debugging, I needed to use the restricted address range. That's when I > noticed that the docs for i2ctransfer were missing an update (patch 1). But > even more surprising, I noticed that the reserved addresses 0x03-0x07 were not > restricted. It seems we all are so used to our lovely i2c-tools that nobody > (including me) never questioned that :) But it should be fixed (patch 2), I > think. > > Open for comments. Happy hacking! I'm no expert in i2c but this matches my understanding of reserved addresses in the specification, feel free to add for the whole series Reviewed-by: Niklas Söderlund <niklas.soderlund+renesas@xxxxxxxxxxxx> > > > Wolfram Sang (2): > tools: i2ctransfer: man: mention -a everywhere > tools: restrict all addresses defined by the standard > > CHANGES | 2 ++ > tools/i2cbusses.c | 2 +- > tools/i2cdetect.8 | 2 +- > tools/i2cdetect.c | 2 +- > tools/i2cdump.8 | 4 ++-- > tools/i2cdump.c | 2 +- > tools/i2cget.8 | 4 ++-- > tools/i2cget.c | 2 +- > tools/i2cset.8 | 4 ++-- > tools/i2cset.c | 2 +- > tools/i2ctransfer.8 | 12 +++++++----- > 11 files changed, 21 insertions(+), 17 deletions(-) > > -- > 2.11.0 > -- Regards, Niklas Söderlund
