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

@@ -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

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)