aboutsummaryrefslogtreecommitdiff
path: root/Documentation/i2c/i2c-stub
diff options
context:
space:
mode:
authorJean Delvare <khali@linux-fr.org>2009-12-06 17:06:30 +0100
committerJean Delvare <khali@linux-fr.org>2009-12-06 17:06:30 +0100
commit6471b68982d3bb1a593c3e183c804ecf830125d3 (patch)
tree9fd3e457e895a7acddafe306aa19b84cb2356958 /Documentation/i2c/i2c-stub
parent38f41f282f1f88b4038f019de51cb95984e569d5 (diff)
downloadlinux-6471b68982d3bb1a593c3e183c804ecf830125d3.tar.gz
i2c-stub: Documentation update
There is nothing sensors-specific to i2c-stub. Signed-off-by: Jean Delvare <khali@linux-fr.org>
Diffstat (limited to 'Documentation/i2c/i2c-stub')
-rw-r--r--Documentation/i2c/i2c-stub4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/i2c/i2c-stub b/Documentation/i2c/i2c-stub
index 326d1ee81e0..fa4b669c166 100644
--- a/Documentation/i2c/i2c-stub
+++ b/Documentation/i2c/i2c-stub
@@ -21,8 +21,8 @@ EEPROMs, among others.
The typical use-case is like this:
1. load this module
- 2. use i2cset (from lm_sensors project) to pre-load some data
- 3. load the target sensors chip driver module
+ 2. use i2cset (from the i2c-tools project) to pre-load some data
+ 3. load the target chip driver module
4. observe its behavior in the kernel log
There's a script named i2c-stub-from-dump in the i2c-tools package which