eeprom 4.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596
  1. Kernel driver eeprom
  2. ====================
  3. Supported chips:
  4. * Any EEPROM chip in the designated address range
  5. Prefix: 'eeprom'
  6. Addresses scanned: I2C 0x50 - 0x57
  7. Datasheets: Publicly available from:
  8. Atmel (www.atmel.com),
  9. Catalyst (www.catsemi.com),
  10. Fairchild (www.fairchildsemi.com),
  11. Microchip (www.microchip.com),
  12. Philips (www.semiconductor.philips.com),
  13. Rohm (www.rohm.com),
  14. ST (www.st.com),
  15. Xicor (www.xicor.com),
  16. and others.
  17. Chip Size (bits) Address
  18. 24C01 1K 0x50 (shadows at 0x51 - 0x57)
  19. 24C01A 1K 0x50 - 0x57 (Typical device on DIMMs)
  20. 24C02 2K 0x50 - 0x57
  21. 24C04 4K 0x50, 0x52, 0x54, 0x56
  22. (additional data at 0x51, 0x53, 0x55, 0x57)
  23. 24C08 8K 0x50, 0x54 (additional data at 0x51, 0x52,
  24. 0x53, 0x55, 0x56, 0x57)
  25. 24C16 16K 0x50 (additional data at 0x51 - 0x57)
  26. Sony 2K 0x57
  27. Atmel 34C02B 2K 0x50 - 0x57, SW write protect at 0x30-37
  28. Catalyst 34FC02 2K 0x50 - 0x57, SW write protect at 0x30-37
  29. Catalyst 34RC02 2K 0x50 - 0x57, SW write protect at 0x30-37
  30. Fairchild 34W02 2K 0x50 - 0x57, SW write protect at 0x30-37
  31. Microchip 24AA52 2K 0x50 - 0x57, SW write protect at 0x30-37
  32. ST M34C02 2K 0x50 - 0x57, SW write protect at 0x30-37
  33. Authors:
  34. Frodo Looijaard <frodol@dds.nl>,
  35. Philip Edelbrock <phil@netroedge.com>,
  36. Jean Delvare <khali@linux-fr.org>,
  37. Greg Kroah-Hartman <greg@kroah.com>,
  38. IBM Corp.
  39. Description
  40. -----------
  41. This is a simple EEPROM module meant to enable reading the first 256 bytes
  42. of an EEPROM (on a SDRAM DIMM for example). However, it will access serial
  43. EEPROMs on any I2C adapter. The supported devices are generically called
  44. 24Cxx, and are listed above; however the numbering for these
  45. industry-standard devices may vary by manufacturer.
  46. This module was a programming exercise to get used to the new project
  47. organization laid out by Frodo, but it should be at least completely
  48. effective for decoding the contents of EEPROMs on DIMMs.
  49. DIMMS will typically contain a 24C01A or 24C02, or the 34C02 variants.
  50. The other devices will not be found on a DIMM because they respond to more
  51. than one address.
  52. DDC Monitors may contain any device. Often a 24C01, which responds to all 8
  53. addresses, is found.
  54. Recent Sony Vaio laptops have an EEPROM at 0x57. We couldn't get the
  55. specification, so it is guess work and far from being complete.
  56. The Microchip 24AA52/24LCS52, ST M34C02, and others support an additional
  57. software write protect register at 0x30 - 0x37 (0x20 less than the memory
  58. location). The chip responds to "write quick" detection at this address but
  59. does not respond to byte reads. If this register is present, the lower 128
  60. bytes of the memory array are not write protected. Any byte data write to
  61. this address will write protect the memory array permanently, and the
  62. device will no longer respond at the 0x30-37 address. The eeprom driver
  63. does not support this register.
  64. Lacking functionality:
  65. * Full support for larger devices (24C04, 24C08, 24C16). These are not
  66. typically found on a PC. These devices will appear as separate devices at
  67. multiple addresses.
  68. * Support for really large devices (24C32, 24C64, 24C128, 24C256, 24C512).
  69. These devices require two-byte address fields and are not supported.
  70. * Enable Writing. Again, no technical reason why not, but making it easy
  71. to change the contents of the EEPROMs (on DIMMs anyway) also makes it easy
  72. to disable the DIMMs (potentially preventing the computer from booting)
  73. until the values are restored somehow.
  74. Use:
  75. After inserting the module (and any other required SMBus/i2c modules), you
  76. should have some EEPROM directories in /sys/bus/i2c/devices/* of names such
  77. as "0-0050". Inside each of these is a series of files, the eeprom file
  78. contains the binary data from EEPROM.