| 1 | Kernel driver `i2c-piix4.o' |
|---|
| 2 | |
|---|
| 3 | Status: Complete and well-tested |
|---|
| 4 | except for Victory66 support which is Alpha. |
|---|
| 5 | |
|---|
| 6 | Supported adapters: |
|---|
| 7 | * Intel 82371AB PIIX4 and PIIX4E |
|---|
| 8 | * Intel 82443MX (440MX) |
|---|
| 9 | Datasheet: Publicly available at the Intel website |
|---|
| 10 | * ServerWorks OSB4, CSB5, CSB6 and HT-1000 southbridges |
|---|
| 11 | Datasheet: Only available via NDA from ServerWorks |
|---|
| 12 | * ATI IXP southbridges IXP200, IXP300, IXP400 |
|---|
| 13 | Datasheet: Not publicly available |
|---|
| 14 | * Standard Microsystems (SMSC) SLC90E66 (Victory66) southbridge |
|---|
| 15 | Datasheet: Publicly available at the SMSC website http://www.smsc.com |
|---|
| 16 | |
|---|
| 17 | Author: Frodo Looijaard <frodol@dds.nl> and Philip Edelbrock |
|---|
| 18 | <phil@netroedge.com> |
|---|
| 19 | |
|---|
| 20 | |
|---|
| 21 | Module Parameters |
|---|
| 22 | ----------------- |
|---|
| 23 | |
|---|
| 24 | * force: int |
|---|
| 25 | Forcibly enable the PIIX4. DANGEROUS! |
|---|
| 26 | * force_addr: int |
|---|
| 27 | Forcibly enable the PIIX4 at the given address. EXTREMELY DANGEROUS! |
|---|
| 28 | * fix_hstcfg: int |
|---|
| 29 | Fix config register. Needed on some boards (Force CPCI735). |
|---|
| 30 | |
|---|
| 31 | |
|---|
| 32 | Description |
|---|
| 33 | ----------- |
|---|
| 34 | |
|---|
| 35 | The PIIX4 (properly known as the 82371AB) is an Intel chip with a lot of |
|---|
| 36 | functionality. Among other things, it implements the PCI bus. One of its |
|---|
| 37 | minor functions is implementing a System Management Bus. This is a true |
|---|
| 38 | SMBus - you can not access it on I2C levels. The good news is that it |
|---|
| 39 | natively understands SMBus commands and you do not have to worry about |
|---|
| 40 | timing problems. The bad news is that non-SMBus devices connected to it |
|---|
| 41 | can confuse it mightily. Yes, this is known to happen... |
|---|
| 42 | |
|---|
| 43 | Cat /proc/pci, and see whether it contains an entry like this: |
|---|
| 44 | |
|---|
| 45 | Bus 0, device 1, function 3: |
|---|
| 46 | Bridge: Intel 82371AB PIIX4 ACPI (rev 1). |
|---|
| 47 | Medium devsel. Fast back-to-back capable. |
|---|
| 48 | |
|---|
| 49 | Bus and device numbers may differ, but the function number must be identical |
|---|
| 50 | (like many PCI devices, the PIIX4 incorporates a number of different |
|---|
| 51 | 'functions', which can be considered as separate devices). If you find such |
|---|
| 52 | an entry, you have a PIIX4 SMBus controller. |
|---|
| 53 | |
|---|
| 54 | On some computers (most notably, some Dells), the SMBus is disabled by |
|---|
| 55 | default. If you use the insmod parameter 'force=1', the kernel module |
|---|
| 56 | will try to enable it. THIS IS VERY DANGEROUS! If the BIOS did not |
|---|
| 57 | set up a correct address for this module, you could get in big trouble |
|---|
| 58 | (read: crashes, data corruption, etc.). Try this only as a last resort |
|---|
| 59 | (try BIOS updates first, for example), and backup first! An even more |
|---|
| 60 | dangerous option is 'force_addr=<IOPORT>'. This will not only enable the |
|---|
| 61 | PIIX4 like 'force' foes, but it will also set a new base I/O port address. |
|---|
| 62 | The SMBus parts of the PIIX4 needs a range of 8 of these addresses to |
|---|
| 63 | function correctly. If these addresses are already reserved by some other |
|---|
| 64 | device, you will get into big trouble! DON'T USE THIS IF YOU ARE NOT VERY |
|---|
| 65 | SURE ABOUT WHAT YOU ARE DOING! |
|---|
| 66 | |
|---|
| 67 | The PIIX4E is just an new version of the PIIX4; it is supported as well. The |
|---|
| 68 | PIIX/PIIX3 does not implement an SMBus or I2C bus, so you can't use this |
|---|
| 69 | driver on those mainboards. |
|---|
| 70 | |
|---|
| 71 | The ServerWorks Southbridges, the Intel 440MX, |
|---|
| 72 | and the Victory766 are identical to the PIIX4 in I2C/SMBus support. |
|---|
| 73 | |
|---|
| 74 | A few OSB4 southbridges are known to be misconfigured by the BIOS. In this |
|---|
| 75 | case, you have you use the fix_hstcfg module parameter. Do not use it |
|---|
| 76 | unless you know you have to, because in some cases it also breaks |
|---|
| 77 | configuration on southbridges that don't need it. |
|---|
