Lines Matching +full:no +full:- +full:eeprom

2 Kernel driver eeprom
7   * Any EEPROM chip in the designated address range
9     Prefix: 'eeprom'
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 -----------
57 This is a simple EEPROM module meant to enable reading the first 256 bytes
58 of an EEPROM (on a SDRAM DIMM for example). However, it will access serial
61 industry-standard devices may vary by manufacturer.
74 Recent Sony Vaio laptops have an EEPROM at 0x57. We couldn't get the
78 software write protect register at 0x30 - 0x37 (0x20 less than the memory
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.
96 * Enable Writing. Again, no technical reason why not, but making it easy
102 ---
105 should have some EEPROM directories in ``/sys/bus/i2c/devices/*`` of names such
106 as "0-0050". Inside each of these is a series of files, the eeprom file
107 contains the binary data from EEPROM.