On Sat, Oct 6, 2012 at 7:56 AM, Mauro Carvalho Chehab <mche...@redhat.com> wrote: > AFAIKT, newer em28xx chips are using this concept. The em28xx-i2c code require > changes to support two I2C buses, and to handle 16 bit eeproms. We never cared > of doing that because we never needed, so far, to read anything from those > devices' eeproms.
I actually wrote the code to read the 16-bit eeprom from the em2874, but removed it before submitting it upstream because I was afraid well-intentioned em28xx users trying to add support for their boards would trash their eeprom. This is because performing a read against a 16-bit eeprom is equivalent to a write on an 8-bit eeprom. Hence if the user didn't know what he/she was doing, and used the 16-bit eeprom code against an older eeprom, the eeprom would get trashed (this actually happened to me once when I was doing the em2874 device support originally). If we really want that code back in the tree, I can dig it up -- but I won't be responsible for users killing their devices. Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
