| Wolfram Sang | 5195e50 | 2009-01-26 21:19:53 +0100 | [diff] [blame^] | 1 | menu "EEPROM support" |
| 2 | |
| 3 | config AT24 |
| 4 | tristate "I2C EEPROMs from most vendors" |
| 5 | depends on I2C && SYSFS && EXPERIMENTAL |
| 6 | help |
| 7 | Enable this driver to get read/write support to most I2C EEPROMs, |
| 8 | after you configure the driver to know about each EEPROM on |
| 9 | your target board. Use these generic chip names, instead of |
| 10 | vendor-specific ones like at24c64 or 24lc02: |
| 11 | |
| 12 | 24c00, 24c01, 24c02, spd (readonly 24c02), 24c04, 24c08, |
| 13 | 24c16, 24c32, 24c64, 24c128, 24c256, 24c512, 24c1024 |
| 14 | |
| 15 | Unless you like data loss puzzles, always be sure that any chip |
| 16 | you configure as a 24c32 (32 kbit) or larger is NOT really a |
| 17 | 24c16 (16 kbit) or smaller, and vice versa. Marking the chip |
| 18 | as read-only won't help recover from this. Also, if your chip |
| 19 | has any software write-protect mechanism you may want to review the |
| 20 | code to make sure this driver won't turn it on by accident. |
| 21 | |
| 22 | If you use this with an SMBus adapter instead of an I2C adapter, |
| 23 | full functionality is not available. Only smaller devices are |
| 24 | supported (24c16 and below, max 4 kByte). |
| 25 | |
| 26 | This driver can also be built as a module. If so, the module |
| 27 | will be called at24. |
| 28 | |
| 29 | endmenu |