Lines Matching +full:write +full:- +full:to +full:- +full:write
7 Addresses scanned: I2C 0x50 - 0x57
20 24C01 1K 0x50 (shadows at 0x51 - 0x57)
21 24C01A 1K 0x50 - 0x57 (Typical device on DIMMs)
22 24C02 2K 0x50 - 0x57
27 24C16 16K 0x50 (additional data at 0x51 - 0x57)
30 Atmel 34C02B 2K 0x50 - 0x57, SW write protect at 0x30-37
31 Catalyst 34FC02 2K 0x50 - 0x57, SW write protect at 0x30-37
32 Catalyst 34RC02 2K 0x50 - 0x57, SW write protect at 0x30-37
33 Fairchild 34W02 2K 0x50 - 0x57, SW write protect at 0x30-37
34 Microchip 24AA52 2K 0x50 - 0x57, SW write protect at 0x30-37
35 ST M34C02 2K 0x50 - 0x57, SW write protect at 0x30-37
41 Jean Delvare <khali@linux-fr.org>,
42 Greg Kroah-Hartman <greg@kroah.com>,
46 -----------
48 This is a simple EEPROM module meant to enable reading the first 256 bytes
52 industry-standard devices may vary by manufacturer.
54 This module was a programming exercise to get used to the new project
59 The other devices will not be found on a DIMM because they respond to more
62 DDC Monitors may contain any device. Often a 24C01, which responds to all 8
69 software write protect register at 0x30 - 0x37 (0x20 less than the memory
70 location). The chip responds to "write quick" detection at this address but
71 does not respond to byte reads. If this register is present, the lower 128
72 bytes of the memory array are not write protected. Any byte data write to
73 this address will write protect the memory array permanently, and the
74 device will no longer respond at the 0x30-37 address. The eeprom driver
84 These devices require two-byte address fields and are not supported.
87 to change the contents of the EEPROMs (on DIMMs anyway) also makes it easy
88 to disable the DIMMs (potentially preventing the computer from booting)
95 as "0-0050". Inside each of these is a series of files, the eeprom file