X-Git-Url: http://git.samba.org/samba.git/?a=blobdiff_plain;f=Documentation%2Fi2c%2Fslave-interface;h=61ed05cd95317f0cb92ce46dd06624ea7936fdb3;hb=82278fc079542a04e076da34546a7d6dc649b0cc;hp=2dee4e2d62df195ee3897e21d0d1e73424a21985;hpb=4ad79562577a3936b08365260f86eeb83156479f;p=sfrench%2Fcifs-2.6.git

diff --git a/Documentation/i2c/slave-interface b/Documentation/i2c/slave-interface
index 2dee4e2d62df..61ed05cd9531 100644
--- a/Documentation/i2c/slave-interface
+++ b/Documentation/i2c/slave-interface
@@ -31,10 +31,13 @@ User manual
 ===========
 
 I2C slave backends behave like standard I2C clients. So, you can instantiate
-them as described in the document 'instantiating-devices'. A quick example for
-instantiating the slave-eeprom driver from userspace at address 0x64 on bus 1:
+them as described in the document 'instantiating-devices'. The only difference
+is that i2c slave backends have their own address space. So, you have to add
+0x1000 to the address you would originally request. An example for
+instantiating the slave-eeprom driver from userspace at the 7 bit address 0x64
+on bus 1:
 
-  # echo slave-24c02 0x64 > /sys/bus/i2c/devices/i2c-1/new_device
+  # echo slave-24c02 0x1064 > /sys/bus/i2c/devices/i2c-1/new_device
 
 Each backend should come with separate documentation to describe its specific
 behaviour and setup.