I think that worked, I can see the device popup in the /sys/bus/i2c/drivers/i2c-slave-eeprom folder, and looking at the uevent file in the created device (1-0028) gives me: DRIVER=i2c-slave-eeprom MODALIAS=i2c:slave-24c02 Sorry to hackle you more but I am still getting the continuous message (when the console log level has changed to 8): i2c-slave-eerpom 1-0028: uevent Should I just ignore this for now and see if I can get the slave support to work or do you think this might be in an issue in my implementation of the slave support in the xilinx driver. Thanks, Tim On Sat, Jun 13, 2015 at 5:49 AM, Wolfram Sang <wsa@xxxxxxxxxxxxx> wrote: > >> I don't think necessarily there is an error in the docs, it was probably my > > Nope, the docs are wrong. Try this: > > echo slave-24c02 0x28 > /sys/bus/i2c/devices/i2c-1/new_device > > That should be it. I am travelling at the moment, so I can't double > check, sadly. But after that, you should have a new device at 1-0028 > bound to the i2c-slave-eeprom driver. > > Thanks for the code! Haven't looked in detail yet, needs some polishing > to match kernel coding style. But as they say, first make it work, then > make it beautiful. > > Good luck! -- Tim Bakker, PhD Research Assistant Virginia Commonwealth University 601 W. Main St. Richmond, VA 23284-3068 Rm. 216 -- 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
