Hi Wolfram,
On Sat, Aug 8, 2015 at 10:33 PM, Wolfram Sang <wsa@xxxxxxxxxxxxx> wrote:
> diff --git a/Documentation/i2c/slave-interface b/Documentation/i2c/slave-interface
> index 2dee4e2d62df19..61ed05cd95317f 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
Does 0x64 still work? It's an ABI since v4.1.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
