Changeset 5140
- Timestamp:
- 03/11/08 11:18:24 (5 years ago)
- Location:
- i2c-tools/trunk
- Files:
-
- 2 modified
-
CHANGES (modified) (1 diff)
-
tools/i2cdump.8 (modified) (2 diffs)
Legend:
- Unmodified
- Added
- Removed
-
i2c-tools/trunk/CHANGES
r5087 r5140 10 10 Fix the timestamp decoding 11 11 i2cdump: Fix I2C block mode error code 12 Remove man page reference to hardware monitoring chips 12 13 i2cset: Final status messages go to stdout 13 14 Return success even when readback fails or doesn't match -
i2c-tools/trunk/tools/i2cdump.8
r4488 r5140 1 .TH I2CDUMP 8 " June 2007"1 .TH I2CDUMP 8 "March 2008" 2 2 .SH NAME 3 3 i2cdump \- examine I2C registers … … 66 66 or no (visible) register at all will most likely see this as a real WRITE, 67 67 resulting in possible misbehavior or corruption. Do not use i2cdump 68 on random addresses. Anyway, it is of little use unless you have an idea of69 what you are looking for and have some general knowledge about hardware 70 monitoring chips internals.68 on random addresses. Anyway, it is of little use unless you have good 69 knowledge of the chip you're working with and an idea of what you are looking 70 for. 71 71 72 72 .SH SEE ALSO
