Lines Matching +full:write +full:- +full:protect
11 Addresses scanned: I2C 0x50 - 0x57
28 24C01 1K 0x50 (shadows at 0x51 - 0x57)
29 24C01A 1K 0x50 - 0x57 (Typical device on DIMMs)
30 24C02 2K 0x50 - 0x57
35 24C16 16K 0x50 (additional data at 0x51 - 0x57)
38 Atmel 34C02B 2K 0x50 - 0x57, SW write protect at 0x30-37
39 Catalyst 34FC02 2K 0x50 - 0x57, SW write protect at 0x30-37
40 Catalyst 34RC02 2K 0x50 - 0x57, SW write protect at 0x30-37
41 Fairchild 34W02 2K 0x50 - 0x57, SW write protect at 0x30-37
42 Microchip 24AA52 2K 0x50 - 0x57, SW write protect at 0x30-37
43 ST M34C02 2K 0x50 - 0x57, SW write protect at 0x30-37
48 - Frodo Looijaard <frodol@dds.nl>,
49 - Philip Edelbrock <phil@netroedge.com>,
50 - Jean Delvare <jdelvare@suse.de>,
51 - Greg Kroah-Hartman <greg@kroah.com>,
52 - IBM Corp.
55 -----------
61 industry-standard devices may vary by manufacturer.
78 software write protect register at 0x30 - 0x37 (0x20 less than the memory
79 location). The chip responds to "write quick" detection at this address but
81 bytes of the memory array are not write protected. Any byte data write to
82 this address will write protect the memory array permanently, and the
83 device will no longer respond at the 0x30-37 address. The eeprom driver
87 ---------------------
94 These devices require two-byte address fields and are not supported.
102 ---
106 as "0-0050". Inside each of these is a series of files, the eeprom file