Changeset 5149 for i2c-tools/trunk/stub/i2c-stub-from-dump.8
- Timestamp:
- 03/19/08 15:04:25 (4 years ago)
- Files:
-
- 1 modified
-
i2c-tools/trunk/stub/i2c-stub-from-dump.8 (modified) (3 diffs)
Legend:
- Unmodified
- Added
- Removed
-
i2c-tools/trunk/stub/i2c-stub-from-dump.8
r5005 r5149 1 .TH I2C-STUB-FROM-DUMP 8 " November 2007"1 .TH I2C-STUB-FROM-DUMP 8 "March 2008" 2 2 .SH NAME 3 3 i2c-stub-from-dump \- feed i2c-stub with a dump file … … 27 27 28 28 Adjust the bus number and chip address for your case. i2cdetect can help 29 you find out their values. 29 you find out their values. If the device uses word (16-bit) register 30 access instead of the traditional byte (8-bit) access, use mode \fBw\fR 31 instead of \fBb\fR. 30 32 31 33 Copy the dump file to system B. … … 41 43 .SH LIMITATIONS 42 44 There are some limitations to the kind of devices that can be handled: 43 .IP \(bu "\w'\(bu'u+1n"44 Device must only use byte register access. i2c-stub supports word45 access but i2c-stub-from-dump doesn't (yet).46 45 .IP \(bu 47 46 Device must not have banks (as most Winbond devices do). 48 47 49 48 .SH SEE ALSO 50 i2cdump(8), i2cdetect(8), i2cset(8)49 i2cdump(8), i2cdetect(8), i2cset(8) 51 50 52 51 .SH AUTHOR
