From 0d1b482ef096e35b0e81f676dd8d55c81f3cfdf5 Mon Sep 17 00:00:00 2001 From: Jean Delvare Date: Tue, 11 Mar 2008 10:18:24 +0000 Subject: [PATCH] Remove reference to hardware monitoring chips. i2cdump works on all I2C/SMBus chips, not just hardware monitoring chips. git-svn-id: http://lm-sensors.org/svn/i2c-tools/trunk@5140 7894878c-1315-0410-8ee3-d5d059ff63e0 --- CHANGES | 1 + tools/i2cdump.8 | 8 ++++---- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/CHANGES b/CHANGES index 07f846d..c0d6e52 100644 --- a/CHANGES +++ b/CHANGES @@ -9,6 +9,7 @@ SVN Print the asset tag Fix the timestamp decoding i2cdump: Fix I2C block mode error code + Remove man page reference to hardware monitoring chips i2cset: Final status messages go to stdout Return success even when readback fails or doesn't match i2c-stub-from-dump: New helper script to use with i2c-stub diff --git a/tools/i2cdump.8 b/tools/i2cdump.8 index 34ed0e7..6241131 100644 --- a/tools/i2cdump.8 +++ b/tools/i2cdump.8 @@ -1,4 +1,4 @@ -.TH I2CDUMP 8 "June 2007" +.TH I2CDUMP 8 "March 2008" .SH NAME i2cdump \- examine I2C registers @@ -65,9 +65,9 @@ starts with WRITING a byte to the chip. On most chips it will be stored in the address pointer register, which is OK, but some chips with a single register or no (visible) register at all will most likely see this as a real WRITE, resulting in possible misbehavior or corruption. Do not use i2cdump -on random addresses. Anyway, it is of little use unless you have an idea of -what you are looking for and have some general knowledge about hardware -monitoring chips internals. +on random addresses. Anyway, it is of little use unless you have good +knowledge of the chip you're working with and an idea of what you are looking +for. .SH SEE ALSO i2cset(8), i2cdetect(8), isadump(8)