diff options
| author | David S. Miller <davem@davemloft.net> | 2008-07-18 05:39:39 -0400 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2008-07-18 05:39:39 -0400 |
| commit | 49997d75152b3d23c53b0fa730599f2f74c92c65 (patch) | |
| tree | 46e93126170d02cfec9505172e545732c1b69656 /Documentation/i2c/busses/i2c-i810 | |
| parent | a0c80b80e0fb48129e4e9d6a9ede914f9ff1850d (diff) | |
| parent | 5b664cb235e97afbf34db9c4d77f08ebd725335e (diff) | |
Merge branch 'master' of master.kernel.org:/pub/scm/linux/kernel/git/torvalds/linux-2.6
Conflicts:
Documentation/powerpc/booting-without-of.txt
drivers/atm/Makefile
drivers/net/fs_enet/fs_enet-main.c
drivers/pci/pci-acpi.c
net/8021q/vlan.c
net/iucv/iucv.c
Diffstat (limited to 'Documentation/i2c/busses/i2c-i810')
| -rw-r--r-- | Documentation/i2c/busses/i2c-i810 | 47 |
1 files changed, 0 insertions, 47 deletions
diff --git a/Documentation/i2c/busses/i2c-i810 b/Documentation/i2c/busses/i2c-i810 deleted file mode 100644 index 778210ee1583..000000000000 --- a/Documentation/i2c/busses/i2c-i810 +++ /dev/null | |||
| @@ -1,47 +0,0 @@ | |||
| 1 | Kernel driver i2c-i810 | ||
| 2 | |||
| 3 | Supported adapters: | ||
| 4 | * Intel 82810, 82810-DC100, 82810E, and 82815 (GMCH) | ||
| 5 | * Intel 82845G (GMCH) | ||
| 6 | |||
| 7 | Authors: | ||
| 8 | Frodo Looijaard <frodol@dds.nl>, | ||
| 9 | Philip Edelbrock <phil@netroedge.com>, | ||
| 10 | Kyösti Mälkki <kmalkki@cc.hut.fi>, | ||
| 11 | Ralph Metzler <rjkm@thp.uni-koeln.de>, | ||
| 12 | Mark D. Studebaker <mdsxyz123@yahoo.com> | ||
| 13 | |||
| 14 | Main contact: Mark Studebaker <mdsxyz123@yahoo.com> | ||
| 15 | |||
| 16 | Description | ||
| 17 | ----------- | ||
| 18 | |||
| 19 | WARNING: If you have an '810' or '815' motherboard, your standard I2C | ||
| 20 | temperature sensors are most likely on the 801's I2C bus. You want the | ||
| 21 | i2c-i801 driver for those, not this driver. | ||
| 22 | |||
| 23 | Now for the i2c-i810... | ||
| 24 | |||
| 25 | The GMCH chip contains two I2C interfaces. | ||
| 26 | |||
| 27 | The first interface is used for DDC (Data Display Channel) which is a | ||
| 28 | serial channel through the VGA monitor connector to a DDC-compliant | ||
| 29 | monitor. This interface is defined by the Video Electronics Standards | ||
| 30 | Association (VESA). The standards are available for purchase at | ||
| 31 | http://www.vesa.org . | ||
| 32 | |||
| 33 | The second interface is a general-purpose I2C bus. It may be connected to a | ||
| 34 | TV-out chip such as the BT869 or possibly to a digital flat-panel display. | ||
| 35 | |||
| 36 | Features | ||
| 37 | -------- | ||
| 38 | |||
| 39 | Both busses use the i2c-algo-bit driver for 'bit banging' | ||
| 40 | and support for specific transactions is provided by i2c-algo-bit. | ||
| 41 | |||
| 42 | Issues | ||
| 43 | ------ | ||
| 44 | |||
| 45 | If you enable bus testing in i2c-algo-bit (insmod i2c-algo-bit bit_test=1), | ||
| 46 | the test may fail; if so, the i2c-i810 driver won't be inserted. However, | ||
| 47 | we think this has been fixed. | ||