X-Git-Url: https://git.sur5r.net/?a=blobdiff_plain;f=README;h=fb8ba0bdaaaa70ba046f5fdcd770310a63b12cc2;hb=40bec4b5a7896d4406d2a7d095d06c0624c24aca;hp=fff6f6bf55bc18bab4dc355192a24a8b75e35ec3;hpb=7eca3463143fb3ca27e8cdd3d3eb7783b6f6948d;p=groeck-it87 diff --git a/README b/README index fff6f6b..fb8ba0b 100644 --- a/README +++ b/README @@ -1,3 +1,14 @@ +DRIVER REMOVAL NOTICE +===================== + +I have been unable to meet support demands for this driver, resulting +in unpleasant experience and frustration for everyone involved. + +Consequently, the driver will be removed from github, effective +August 1, 2018. Interested parties are encouraged to clone the driver +before that time and to start maintaining it on their own. + + Kernel driver it87 ================== @@ -6,9 +17,21 @@ Supported chips: Prefix: 'it8603' Addresses scanned: from Super I/O config space (8 I/O ports) Datasheet: Not publicly available + * IT8613E + Prefix: 'it8613' + Addresses scanned: from Super I/O config space (8 I/O ports) + Datasheet: Not publicly available * IT8620E Prefix: 'it8620' Addresses scanned: from Super I/O config space (8 I/O ports) + * IT8622E + Prefix: 'it8622' + Addresses scanned: from Super I/O config space (8 I/O ports) + Datasheet: Not publicly available + * IT8625E + Prefix: 'it8625' + Addresses scanned: from Super I/O config space (8 I/O ports) + Datasheet: Not publicly available * IT8628E Prefix: 'it8628' Addresses scanned: from Super I/O config space (8 I/O ports) @@ -81,6 +104,40 @@ Supported chips: Authors: Christophe Gauthron Jean Delvare + Guenter Roeck + + +Building & Installing +--------------------- + +* make clean +* make +* sudo make install + + +Using DKMS +---------- + +To install: + +* sudo make dkms + +To remove: + +* sudo make dkms_clean + +Notes: + +* The module does not provide a real version number, so `git describe --long` + is used to create one. This means that anything that changes the git state + will change the version. `make dkms_clean` should be run before making a + commit or an update with `git pull` as the Makefile is currently unable to + track the last installed version to replace it. If this doesn't happen, the + old version will need to be manually removed from dkms, before installing + the updated module. + Something like `dkms remove -m it87 -v --all`, followed by + `rm -rf /usr/src/it87-`, should do. + `dkms status it87` can be used to list the installed versions. Module Parameters @@ -102,6 +159,26 @@ Module Parameters misconfigured by BIOS - PWM values would be inverted. This option tries to fix this. Please contact your BIOS manufacturer and ask him for fix. +* force_id + + Force chip ID to specified value. Should only be used for testing. + +* ignore_resource_conflict + + Similar to acpi_enforce_resources=lax, but only affects this driver. + ACPI resource conflicts are ignored if this parameter is provided and + set to 1. + Provided since there are reports that system-wide acpi_enfore_resources=lax + can result in boot failures on some systems. + Note: This is inherently risky since it means that both ACPI and this driver + may access the chip at the same time. This can result in race conditions and, + worst case, result in unexpected system reboots. + +* mmio + + If set to 1, the driver uses MMIO to access the chip if supported. This is + faster and less risky (untested!). + Hardware Interfaces ------------------- @@ -117,10 +194,10 @@ motherboard models. Description ----------- -This driver implements support for the IT8603E, IT8620E, IT8623E, IT8628E, -IT8705F, IT8712F, IT8716F, IT8718F, IT8720F, IT8721F, IT8726F, IT8728F, IT8732F, -IT8758E, IT8771E, IT8772E, IT8781F, IT8782F, IT8783E/F, IT8786E, IT8790E, and -SiS950 chips. +This driver implements support for the IT8603E, IT8620E, IT8622E, IT8623E, +IT8628E, IT8705F, IT8712F, IT8716F, IT8718F, IT8720F, IT8721F, IT8726F, IT8728F, +IT8732F, IT8758E, IT8771E, IT8772E, IT8781F, IT8782F, IT8783E/F, IT8786E, +IT8790E, and SiS950 chips. These chips are 'Super I/O chips', supporting floppy disks, infrared ports, joysticks and other miscellaneous stuff. For hardware monitoring, they @@ -272,3 +349,66 @@ temperature for thermal diodes or diode-connected thermal transistors. If a temperature sensor is configured for thermistors, the attribute values are ignored. If the thermal sensor type is Intel PECI, the temperature offset must be programmed to the critical CPU temperature. + +Preliminary support +------------------- + +Support for IT8607E is preliminary. Voltage readings, temperature readings, +fan control, and fan speed measurements may be wrong and/or missing. +Fan control and fan speed may be enabled and reported for non-existing +fans. Please report any problems and inconsistencies. + +Reporting information for unsupported chips +------------------------------------------- + +If the chip in your system is not yet supported by the driver, please provide +the following information. + +First, run sensors-detect. It will tell you something like + + Probing for Super-I/O at 0x2e/0x2f + ... + Trying family `ITE'... Yes + Found unknown chip with ID 0x8665 + (logical device 4 has address 0x290, could be sensors) + +With this information, run the following commands. + +sudo isadump -k 0x87,0x01,0x55,0x55 0x2e 0x2f 7 +sudo isadump 0x295 0x296 + +and report the results. + +The addresses in the first command are from "Probing for Super-I/O at +0x2e/0x2f". Use those addresses in the first command. + sudo isadump -k 0x87,0x01,0x55,0x55 0x2e 0x2f 7 + +The addresses in the second command are from "has address 0x290". +Add 5 and 6 to this address for the next command. + sudo isadump 0x295 0x296 + +Next, force-install the driver by providing one of the already supported chips +as forced ID. Useful IDs to test are 0x8622, 0x8628, 0x8728, and 0x8732, though +feel free to test more IDs. For each ID, instantiate the driver as follows +(this example is instantiating driver with ID 0x8622). + sudo modprobe it87 force_id=0x8622 +After entering this command, run the "sensors" command and provide the output. +Then unload the driver with + sudo modprobe -r it87 +Repeat with different chip IDs, and report each result. + +Please also report your board type as well as voltages and fan settings from +the BIOS. If possible, connect fans to different fan headers and let us know +if all fans are detected and reported. + +This information _might_ give us enough information to add experimental support +for the chip in question. No guarantees, though - unless a datasheet is +available, something is likely to be wrong. + +A note on sensors-detect +======================== + +There is a persistent perception that changes in this driver would have impact +on the output of sensors-detect. This is not the case. sensors-detect is an +independent application. Changes in this driver do not affect sensors-detect, +and changes in sensors-detect do not affect this driver.