Hello Davide, it was already discussed that writing to EEPROMs will not be included in the mainline kernel (it creates the possibility to destroy RAM modules).
Besides, your driver uses the old I2C-binding model and other soon to-be-removed stuff like .id's. You might also consider using David Brownell's AT24 driver: http://lists.lm-sensors.org/pipermail/i2c/2007-May/001208.html (Side note to David: I already worked on adding platform_data, just need to test it in a quiet minute.) To all: Surely a lot of people need an eeprom driver with write capabilities, especially in the embedded world. I think it would be a good idea to make David's driver more visible. This wheel was probably reinvented too many times already (we also had a custom driver in our company). EEPROMs can be nasty, so one central driver would also be very good to collect all the quirks. To make a start I would suggest the following: Give the AT24 driver a repository (my company would provide this, if wanted/needed). Place a comment in mainline/eeprom.c (and maybe Kconfig?) that an advanced driver exists at this repository. Opinions? Especially David? All the best, Wolfram -- Dipl.-Ing. Wolfram Sang | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry
signature.asc
Description: Digital signature
_______________________________________________ i2c mailing list [email protected] http://lists.lm-sensors.org/mailman/listinfo/i2c
