Lines Matching +full:write +full:- +full:protect

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
42         Greg Kroah-Hartman <greg@kroah.com>,
46 -----------
52 industry-standard devices may vary by manufacturer.
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
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.
95 as "0-0050". Inside each of these is a series of files, the eeprom file