From 95996b46388fa2555a2abd1e581dc2c94711a527 Mon Sep 17 00:00:00 2001 From: Jean Delvare Date: Wed, 2 May 2007 10:35:14 +0000 Subject: [PATCH] Delete mkpatch and all references thereto. The kernel modules will soon be removed from the tree so there won't be anything left to generate a patch from. git-svn-id: http://lm-sensors.org/svn/lm-sensors/branches/lm-sensors-3.0.0@4383 7894878c-1315-0410-8ee3-d5d059ff63e0 --- CHANGES | 1 + INSTALL | 115 +--- Makefile | 1 - README.directories | 2 - doc/developers/new_drivers | 27 +- doc/mkpatch | 82 --- kernel/busses/Module.mk | 2 - kernel/chips/Module.mk | 2 - mkpatch/Config.in | 69 -- mkpatch/FILES | 72 -- mkpatch/INCLUDES | 2 - mkpatch/Module.mk | 26 - mkpatch/mkpatch.pl | 1341 ------------------------------------ 13 files changed, 13 insertions(+), 1729 deletions(-) delete mode 100644 doc/mkpatch delete mode 100644 mkpatch/Config.in delete mode 100644 mkpatch/FILES delete mode 100644 mkpatch/INCLUDES delete mode 100644 mkpatch/Module.mk delete mode 100755 mkpatch/mkpatch.pl diff --git a/CHANGES b/CHANGES index 93ac19ee..b2b48d61 100644 --- a/CHANGES +++ b/CHANGES @@ -8,6 +8,7 @@ SVN HEAD Add dme1737 support Man page sensors.conf.5: Update the chip statement section Program isadump: Detect when address bit 7 is a busy flag + Program mkpatch: Delete Program pwmconfig: Use smaller steps for low PWM values Program rrd: Support only hwmon class devices Look for rrd in /usr/bin by default diff --git a/INSTALL b/INSTALL index 7bf043ae..db1199f4 100644 --- a/INSTALL +++ b/INSTALL @@ -18,34 +18,11 @@ FOR 2.5/2.6 KERNELS, do not attempt to compile the modules in this package. ============================================================================= These are the installation instruction for the lm_sensors package. -There are two ways in which you can compile and install this package. -Option 1 is much easier and is recommended. - - 1. Complete separate from kernel compilation - (only for 2.4 kernels 2.4.10 or later) - This will generate a set of modules which can be inserted and removed - as needed; nothing will be written into the kernel tree; - - 2. Patching of the kernel - (only for 2.4 kernels 2.4.13 or later) - This will patch your kernel source tree. You must recompile your kernel - to take advantage of this. But it makes it possible to compile drivers - into the kernel itself, instead of having to add them as modules. - ** AFTER YOU COMPILED AND INSTALLED YOUR KERNEL, YOU WILL STILL HAVE TO - ** COMPILE THIS PACKAGE TO GET THE USERLAND UTILITIES! - ** NOT ALL MODULES ARE PATCHED INTO THE KERNEL. SEE BELOW. - - - -Each of these ways will be described below in detail. - NOTE: MAKE SURE YOU HAVE THE I2C-ALGO-BIT DRIVER (PART OF THE I2C PACKAGE) COMPILED INTO YOUR KERNEL OR AVAILABLE AS A MODULE; SOME I2C/SMBUS MASTER DRIVERS DEPEND ON IT! -NOTE: IN EACH CASE, YOU WILL HAVE TO GET AND INSTALL THE I2C PACKAGE FIRST! - SET COMPILE_KERNEL TO 0 IN THE MAIN MAKEFILE FOR OPTION 2, UNLESS - YOU NEED ALPHA OR BETA DRIVERS (SEE BELOW) +NOTE: YOU WILL HAVE TO GET AND INSTALL THE I2C PACKAGE FIRST! NOTE: PLEASE READ THE DOCUMENTATION IN THE DOC SUBDIRECTORY IF YOU GET STUCK! @@ -58,24 +35,7 @@ any 2.4 kernel (and will never be). Therefore, you must download and install the i2c package with the same version number or higher as this lm_sensors package. -All i2c components are distributed in -a separate package. There are install instructions in that package. If -you want to use compilation option 2 (patching the kernel) for lm_sensors, -you will have to use compilation option 3 (patching the kernel) for i2c -too. If you want to use compilation option 1 (compiling as modules) for -lm_sensors, you may use either compilation option 1 or 2 (compiling as -modules) or compilation option 3 (patching the kernel for i2c). See the -table below. - - LM_SENSORS -I2C | option 1 (modules) option 2 (patch kernel) --------------------------+------------------------------------------------ -option 1 (modules) | YES NO -option 2 (modules) | YES YES -option 3 (patch kernel) | YES YES - - -If you use compilation option 1 (compiling as modules) for lm_sensors, you +You will have to make very sure the correct i2c header files are found. If you get weird compilation errors, this is almost certainly going wrong. The i2c header files are in a i2c subdirectory of either /usr/local/include @@ -84,12 +44,9 @@ options 2 and 3). Especially if you have in the past placed the header files in /usr/local/include, this will probably go wrong. See below on how to fix this. -NOTE: option 3 only works with 2.4 kernels 2.4.13 or later; - options 1 and 2 only work with 2.4 kernels 2.4.10 or later. - -Mixing old and new, and using beta drivers (compilation option 1) -================================================================= +Mixing old and new, and using beta drivers +========================================== It is possible that you are running a previously patched kernel, or a very new kernel which already has limited or full i2c or lm_sensors @@ -109,20 +66,14 @@ On the other hand, if you know what you are doing, compilation will be smart. Drivers that are compiled right into your kernel will not be compiled as a module again. You could do nothing with them anyway. -Sometimes, you want to patch your kernel, but find that certain alpha -or beta drivers are not included in the patch. This is on purpose: we -do not want to polute the kernel tree with things of which we are not -confident they work. In this case, patch the kernel, compile it, and -then compile lm_sensors with COMPILE_KERNEL set to 1. - -Having a proper kernel tree (compilation option 1) -================================================== +Having a proper kernel tree +=========================== Usually, if you compile a user-space application, you can get away with having a different version of the kernel running than the version of the kernel header files against which you compiled it. But a perfect match -is needed for the first two compilation options above. +is needed here. Let's say you want to use the lm_sensors modules with the kernel 2.4.32 you are running now. What you need, is the original tree in which you @@ -149,8 +100,8 @@ as distributed on ftp://ftp.kernel/org/pub/linux/kernel, and not one patched by your distribution. -Separate from kernel compilation (compilation option 1) -======================================================= +Compilation +=========== This will compile and install the complete lm_sensors package. Though nothing is written to your kernel tree, a proper tree is still needed @@ -176,8 +127,8 @@ information, which is regenerated on the spot. Please continue reading this file before you start compiling. -Makefile configuration variables (compilation option 1) -============================================================== +Makefile configuration variables +================================ SHELL (default: /bin/sh) You may have to specify the full path to Bash here, if /bin/sh is some @@ -187,16 +138,6 @@ KERNELVERSION The version of the currently running kernel. LINUX (default: /lib/modules/$(KERNELVERSION)/build) The location of your kernel tree. -COMPILE_KERNEL - Determine whether you want to consider the kernel modules for compilation - at all. By default, compilation option 1 will only compile and install - those modules which are not built into the kernel. - If some modules are built into your kernel, and this package is much - newer, you may find you can not insert the newly compiled modules. - Sorry. - You may want to set this to 0 if you have just patched and compiled - your kernel using the same version of this package, and just want to - compile the user-space tools. I2C_HEADERS (default: /usr/local/include) This lists where the i2c headers are found. If you used compilation option 1 for the i2c package, the default will be right. If you used @@ -245,40 +186,6 @@ MANGRP (default: root) Group of manual pages. -Patching the kernel (compilation option 2) -========================================== - -There is a special script which should be able to generate diffs against -any 2.4 kernel (2.4.10 or later). Please report any problems to our -mailing list. It *is* safe to run it if your kernel already has the -lm_sensors drivers. It will only work if you applied the i2c patches first. - -** Only a subset of the modules in lm_sensors are patched into the ** -** kernel by the script. See the file mkpatch/FILES to see if the ** -** modules you need are included. If a module you need is NOT listed ** -** in mkpatch/FILES, it will not be patched, and you MUST use option 1. ** -** If you are not sure what modules you need, run `sensors-detect' first. ** - -The kernel diffs are generated by the program `mkpatch.pl' in the mkpatch -subdirectory. It needs two arguments: the first one is the root of the -lm_sensors package, the second one is the root of the kernel tree against -which the diffs will be generated. For example: - cd /tmp/lm_sensors-2.10.0 - mkpatch/mkpatch.pl . /usr/src/linux > /tmp/sensors-2.10.0.patch -You can apply the diffs as usual: - cd /usr/src/linux - patch -p1 -E < /tmp/sensors-2.10.0.patch -Generation and application can easily be done in one step: - mkpatch/mkpatch.pl . /usr/src/linux | patch -p1 -E -d /usr/src/linux -The generated diffs are of course only valid for the kernel version -against which mkpatch.pl was run. - -Once you have applied the patches, you can configure and compile your -kernel as usual. You will see the sensors configuration screen under the -`Character Devices' menu in menuconfig, but it will only be available -if you selected base I2C support. - - Using the sensors package ========================= diff --git a/Makefile b/Makefile index 65665e9d..0f82fe1e 100644 --- a/Makefile +++ b/Makefile @@ -176,7 +176,6 @@ ifneq ($(MAKECMDGOALS),user_uninstall) ifneq ($(MAKECMDGOALS),package) ifneq ($(MAKECMDGOALS),userpackage) ifneq ($(MAKECMDGOALS),manhtml) -SRCDIRS += mkpatch SRCDIRS += kernel kernel/busses kernel/chips endif endif diff --git a/README.directories b/README.directories index a2b996ec..00adce1a 100644 --- a/README.directories +++ b/README.directories @@ -8,8 +8,6 @@ The directories within this package: The kernel modules: I2C/SMBus master drivers, and sensor chip drivers. * lib The user-space sensors support library code. -* mkpatch - A script for creating a kernel patch. * prog Several supporting programs. Includes programs for detecting installed hardware and recommending specific modules to install. diff --git a/doc/developers/new_drivers b/doc/developers/new_drivers index 014b5447..db28421e 100644 --- a/doc/developers/new_drivers +++ b/doc/developers/new_drivers @@ -58,8 +58,7 @@ steps apply. * Add the driver to the Module.mk (the makefile). Usually, you can just add it to KERNEL{CHIPS,DRIVERS}TARGETS in the - Module.mk file in the directory itself. Put it at the beginning, - where the comment says to put drivers NOT included in mkpatch. + Module.mk file in the directory itself. * Make sure it compiles cleanly. Check compilation with 'make DEBUG=1' if you use debugging @@ -143,24 +142,6 @@ Checklist for us to do on the webpage: * Update entry on 'new drivers' page ---------------------------------------------------------------------- -Checklist for mkpatch support, after the driver is tested and stable: - -* Add .c file to mkpatch/FILES. - -* Add makefile entry in mkpatch/mkpatch.pl (2 places - old and new formats). - (don't bother with old format, obsolete) - -* Add config help to mkpatch/mkpatch.pl. - -* Add config entry to mkpatch/Config.in (chip drivers only) - -* Add config entry in mkpatch/mkpatch.pl (bus drivers only) - -* Move .o reference in kernel/[chips,busses]/Module.mk - from first to second section. - - --------------------------------------------------------------------- Checklist for _adding_ support for a chip to an _existing_ driver: @@ -173,12 +154,6 @@ Checklist for _adding_ support for a chip to an _existing_ driver: * Add entries for the new prefix to etc/sensors.conf.eg (chip drivers only). -* Update config help in mkpatch/mkpatch.pl. - -* Update config entry in mkpatch/Config.in (chip drivers only) - -* Update config entry in mkpatch/mkpatch.pl (bus drivers only) - * Update doc/[chips,busses]/xxx file * Update doc/chips/SUMMARY file (chip drivers only) diff --git a/doc/mkpatch b/doc/mkpatch deleted file mode 100644 index c5664e4d..00000000 --- a/doc/mkpatch +++ /dev/null @@ -1,82 +0,0 @@ -This file documents how the `mkpatch' program works. ------------------------------------------------------------- - -QUICKSTART ----------- - mkpatch/mkpatch.pl . /usr/src/linux > /tmp/patch - cd /usr/src/linux - patch -p1 < /tmp/patch - - -USAGE ------ - -mkpatch compares the newest lm_sensors sources with what is found in a kernel, -and generates a set of diffs. These diffs can be applied to that kernel, -after which the kernel is synchronized with the current lm_sensors sources. - -You should generally run mkpatch against a kernel tree that has been patched -with the newest I2C sources. Check the lm_sensors "Download" page for -information on dependencies between lm_sensors and i2c versions. - -mkpatch needs two arguments. The first is the root of the lm_sensors package, -the second is the root of Linux kernel tree. For example: - cd /tmp/lm_sensors-2.4.0 - mkpatch/mkpatch . /usr/src/linux - -The patch file is written to stdout; any errors are written to stderr. -So you will want to capture the output: - mkpatch/mkpatch . /usr/src/linux > /tmp/lm_sensors-diffs - -Later on, you will want to apply the diffs: - cd /usr/src/linux - patch -p1 -E < /tmp/lm_sensors-diffs - -Of course, this can be combined: - mkpatch/mkpatch . /usr/src/linux | patch -d /usr/src/linux -p1 -E - - -IMPLEMENTATION DETAILS ----------------------- - -mkpatch uses several files in the mkpatch subdirectory. The location of -these files is hardcoded in the program, but all other files used are -specified in these files, and can easily be changed. Used files are: - FILES - A list of files that will be considered by mkpatch. Each line contains - two filenames, separated by whitespace. The first is the name and - location (relative to the lm_sensors package root) of the lm_sensors - file, the second is the name and location (relative to the kernel root) of - the kernel file. A diff will be created between these two files. - INCLUDES - A list of include file changes. Each line contains two strings that - can be found after a `#include' statement. All occurences of the - first string will be changed to the second, for all lm_sensors files in - FILES, before the normal diff is generated. This allow us to use - `#include "sensors.h"' when compiling in the package tree, and - `#include ' in the kernel tree. - Makefile, Config.in - These files are new and will be copied to the appropriate place as - specified in FILES. - -mkpatch does several things: - * For each file pair as specified in FILES, it creates a diff between - them, but before that is done, it changes `#include' lines in the - lm_sensors file as specified in INCLUDES - * It handles several special files, that have to be scanned explicitly - to generate diffs to for them - -The generated diffs have specific headers. It will seem as if the old -kernel was contained in the `linux-old' directory, and the new patched -kernel in the `linux' directory, regardless of where the kernel was -actually located. - -Most intricate are the special files that are handled. These special -files were already present in the kernel, but had to be patched. Because -they can change between kernel versions, I had to scan them by hand to -find where the new code should be inserted. Each file has documented -what actually happens. - - ------------- -This file is Copyright (c) 1999 by Frodo Looijaard diff --git a/kernel/busses/Module.mk b/kernel/busses/Module.mk index 39e8d139..4b6fc1ff 100644 --- a/kernel/busses/Module.mk +++ b/kernel/busses/Module.mk @@ -23,7 +23,6 @@ KERNELBUSSESDIR := $(MODULE_DIR) # Regrettably, even 'simply expanded variables' will not put their currently # defined value verbatim into the command-list of rules... -# These targets are NOT included in 'mkpatch' ... KERNELBUSSESTARGETS := ifeq ($(shell if grep -q '^CONFIG_IPMI_HANDLER=' $(LINUX)/.config; then echo 1; fi),1) #doesn't work yet @@ -31,7 +30,6 @@ ifeq ($(shell if grep -q '^CONFIG_IPMI_HANDLER=' $(LINUX)/.config; then echo 1; KERNELBUSSESTARGETS += $(MODULE_DIR)/i2c-ipmi.o endif -# These targets ARE included in 'mkpatch' ... ifneq ($(shell if grep -q '^CONFIG_I2C_ALI1535=y' $(LINUX)/.config; then echo 1; fi),1) KERNELBUSSESTARGETS += $(MODULE_DIR)/i2c-ali1535.o endif diff --git a/kernel/chips/Module.mk b/kernel/chips/Module.mk index f8a7485a..0173a406 100644 --- a/kernel/chips/Module.mk +++ b/kernel/chips/Module.mk @@ -24,7 +24,6 @@ KERNELCHIPSDIR := $(MODULE_DIR) # Regrettably, even 'simply expanded variables' will not put their currently # defined value verbatim into the command-list of rules... -# These targets are NOT included in 'mkpatch' KERNELCHIPSTARGETS := ifeq ($(shell if grep -q '^CONFIG_IPMI_HANDLER=' $(LINUX)/.config; then echo 1; fi),1) KERNELCHIPSTARGETS += $(MODULE_DIR)/bmcsensors.o @@ -37,7 +36,6 @@ KERNELCHIPSTARGETS += $(MODULE_DIR)/smartbatt.o KERNELCHIPSTARGETS += $(MODULE_DIR)/smbus-arp.o -# These targets ARE included in 'mkpatch' ifneq ($(shell if grep -q '^CONFIG_SENSORS_ADM1021=y' $(LINUX)/.config; then echo 1; fi),1) KERNELCHIPSTARGETS += $(MODULE_DIR)/adm1021.o endif diff --git a/mkpatch/Config.in b/mkpatch/Config.in deleted file mode 100644 index 3f11a043..00000000 --- a/mkpatch/Config.in +++ /dev/null @@ -1,69 +0,0 @@ -# -# Sensor device configuration -# All depend on CONFIG_I2C_PROC. -# ISA-only devices depend on CONFIG_I2C_ISA also. -# - -if [ "$CONFIG_I2C" = "m" -o "$CONFIG_I2C" = "y" ] ; then -if [ "$CONFIG_I2C_PROC" = "m" -o "$CONFIG_I2C_PROC" = "y" ] ; then - mainmenu_option next_comment - comment 'Hardware sensors support' - - dep_mbool 'Hardware sensors support' CONFIG_SENSORS $CONFIG_I2C $CONFIG_I2C_PROC - - if [ "$CONFIG_SENSORS" != "n" ]; then - dep_tristate ' Analog Devices ADM1021 and compatibles' CONFIG_SENSORS_ADM1021 $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' Analog Devices ADM1024' CONFIG_SENSORS_ADM1024 $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' Analog Devices ADM1025' CONFIG_SENSORS_ADM1025 $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' Analog Devices ADM1026' CONFIG_SENSORS_ADM1026 $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' Analog Devices ADM1030, ADM1031' CONFIG_SENSORS_ADM1031 $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' Analog Devices ADM9240 and compatibles' CONFIG_SENSORS_ADM9240 $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' Asus ASB100' CONFIG_SENSORS_ASB100 $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' Dallas DS1621 and DS1625' CONFIG_SENSORS_DS1621 $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' Fintek F71805F' CONFIG_SENSORS_F71805F $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' Fujitsu-Siemens Hermes' CONFIG_SENSORS_FSCHER $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' Fujitsu-Siemens Poseidon' CONFIG_SENSORS_FSCPOS $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' Fujitsu-Siemens Scylla' CONFIG_SENSORS_FSCSCY $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' Genesys Logic GL518SM' CONFIG_SENSORS_GL518SM $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' Genesys Logic GL520SM' CONFIG_SENSORS_GL520SM $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' HP Maxilife' CONFIG_SENSORS_MAXILIFE $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' Intel Xeon Thermal Sensor' CONFIG_SENSORS_XEONTEMP $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' ITE 8705/8712, SiS950' CONFIG_SENSORS_IT87 $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' Maxim MAX1619' CONFIG_SENSORS_MAX1619 $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' Maxim MAX6650, MAX6651' CONFIG_SENSORS_MAX6650 $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' Myson MTP008' CONFIG_SENSORS_MTP008 $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' National Semiconductor LM63' CONFIG_SENSORS_LM63 $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' National Semiconductor LM75 and compatibles' CONFIG_SENSORS_LM75 $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' National Semiconductor LM78' CONFIG_SENSORS_LM78 $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' National Semiconductor LM80' CONFIG_SENSORS_LM80 $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' National Semiconductor LM83 and compatibles' CONFIG_SENSORS_LM83 $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' National Semiconductor LM85, Analog Devices ADM1027' CONFIG_SENSORS_LM85 $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' National Semiconductor LM87' CONFIG_SENSORS_LM87 $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' National Semiconductor LM90 and compatibles' CONFIG_SENSORS_LM90 $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' National Semiconductor LM92' CONFIG_SENSORS_LM92 $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' National Semiconductor LM93' CONFIG_SENSORS_LM93 $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' National Semiconductor PC8736x Sensors' CONFIG_SENSORS_PC87360 $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' Silicon Integrated Systems Corp. SiS5595' CONFIG_SENSORS_SIS5595 $CONFIG_I2C $CONFIG_I2C_PROC $CONFIG_I2C_ISA - dep_tristate ' SMSC47M1xx Integrated Sensors' CONFIG_SENSORS_SMSC47M1 $CONFIG_I2C $CONFIG_I2C_PROC $CONFIG_I2C_ISA - dep_tristate ' Texas Instruments THMC50 and compatibles' CONFIG_SENSORS_THMC50 $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' VIA 686a Integrated Hardware Monitor' CONFIG_SENSORS_VIA686A $CONFIG_I2C $CONFIG_I2C_PROC $CONFIG_I2C_ISA - dep_tristate ' VIA VT1211 Integrated Sensors' CONFIG_SENSORS_VT1211 $CONFIG_I2C $CONFIG_I2C_PROC $CONFIG_I2C_ISA - dep_tristate ' VIA VT8231 Integrated Sensors' CONFIG_SENSORS_VT8231 $CONFIG_I2C $CONFIG_I2C_PROC $CONFIG_I2C_ISA - dep_tristate ' Winbond W83781D, W83782D, W83783S, W83627HF, Asus AS99127F' CONFIG_SENSORS_W83781D $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' Winbond W83792D' CONFIG_SENSORS_W83792D $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' Winbond W83627HF, W83627THF, W83637HF, W83687THF, W83697HF' CONFIG_SENSORS_W83627HF $CONFIG_I2C $CONFIG_I2C_PROC $CONFIG_I2C_ISA - dep_tristate ' Winbond W83L785TS-S' CONFIG_SENSORS_W83L785TS $CONFIG_I2C $CONFIG_I2C_PROC - bool 'Other I2C devices' CONFIG_SENSORS_OTHER - if [ "$CONFIG_SENSORS_OTHER" = "y" ] ; then - dep_tristate ' Brooktree BT869 Video Modulator' CONFIG_SENSORS_BT869 $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' DDC Monitor EDID EEPROM' CONFIG_SENSORS_DDCMON $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' EEprom (DIMM) reader ' CONFIG_SENSORS_EEPROM $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' Matrix-Orbital LCD Displays' CONFIG_SENSORS_MATORB $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' Philips PCF8574 Parallel I/O' CONFIG_SENSORS_PCF8574 $CONFIG_I2C $CONFIG_I2C_PROC - dep_tristate ' Philips PCF8591 D/A and A/D' CONFIG_SENSORS_PCF8591 $CONFIG_I2C $CONFIG_I2C_PROC - fi - fi - endmenu -fi -fi - diff --git a/mkpatch/FILES b/mkpatch/FILES deleted file mode 100644 index 73fff819..00000000 --- a/mkpatch/FILES +++ /dev/null @@ -1,72 +0,0 @@ -kernel/busses/i2c-ali1535.c drivers/i2c/i2c-ali1535.c -kernel/busses/i2c-ali15x3.c drivers/i2c/i2c-ali15x3.c -kernel/busses/i2c-ali1563.c drivers/i2c/i2c-ali1563.c -kernel/busses/i2c-amd756.c drivers/i2c/i2c-amd756.c -kernel/busses/i2c-amd756-s4882.c drivers/i2c/i2c-amd756-s4882.c -kernel/busses/i2c-amd8111.c drivers/i2c/i2c-amd8111.c -kernel/busses/i2c-hydra.c drivers/i2c/i2c-hydra.c -kernel/busses/i2c-i801.c drivers/i2c/i2c-i801.c -kernel/busses/i2c-i810.c drivers/i2c/i2c-i810.c -kernel/busses/i2c-isa.c drivers/i2c/i2c-isa.c -kernel/busses/i2c-nforce2.c drivers/i2c/i2c-nforce2.c -kernel/busses/i2c-piix4.c drivers/i2c/i2c-piix4.c -kernel/busses/i2c-savage4.c drivers/i2c/i2c-savage4.c -kernel/busses/i2c-sis5595.c drivers/i2c/i2c-sis5595.c -kernel/busses/i2c-tsunami.c drivers/i2c/i2c-tsunami.c -kernel/busses/i2c-via.c drivers/i2c/i2c-via.c -kernel/busses/i2c-viapro.c drivers/i2c/i2c-viapro.c -kernel/busses/i2c-voodoo3.c drivers/i2c/i2c-voodoo3.c -kernel/busses/i2c-sis630.c drivers/i2c/i2c-sis630.c -kernel/busses/i2c-sis645.c drivers/i2c/i2c-sis645.c -kernel/chips/adm1021.c drivers/sensors/adm1021.c -kernel/chips/adm1024.c drivers/sensors/adm1024.c -kernel/chips/adm1025.c drivers/sensors/adm1025.c -kernel/chips/adm1026.c drivers/sensors/adm1026.c -kernel/chips/adm1031.c drivers/sensors/adm1031.c -kernel/chips/adm9240.c drivers/sensors/adm9240.c -kernel/chips/asb100.c drivers/sensors/asb100.c -kernel/chips/bt869.c drivers/sensors/bt869.c -kernel/chips/ddcmon.c drivers/sensors/ddcmon.c -kernel/chips/ds1621.c drivers/sensors/ds1621.c -kernel/chips/eeprom.c drivers/sensors/eeprom.c -kernel/chips/f71805f.c drivers/sensors/f71805f.c -kernel/chips/fscher.c drivers/sensors/fscher.c -kernel/chips/fscpos.c drivers/sensors/fscpos.c -kernel/chips/fscscy.c drivers/sensors/fscscy.c -kernel/chips/gl518sm.c drivers/sensors/gl518sm.c -kernel/chips/gl520sm.c drivers/sensors/gl520sm.c -kernel/chips/it87.c drivers/sensors/it87.c -kernel/chips/lm63.c drivers/sensors/lm63.c -kernel/chips/lm75.h drivers/sensors/lm75.h -kernel/chips/lm75.c drivers/sensors/lm75.c -kernel/chips/lm78.c drivers/sensors/lm78.c -kernel/chips/lm80.c drivers/sensors/lm80.c -kernel/chips/lm83.c drivers/sensors/lm83.c -kernel/chips/lm85.c drivers/sensors/lm85.c -kernel/chips/lm87.c drivers/sensors/lm87.c -kernel/chips/lm90.c drivers/sensors/lm90.c -kernel/chips/lm92.c drivers/sensors/lm92.c -kernel/chips/lm93.c drivers/sensors/lm93.c -kernel/chips/lm93.h drivers/sensors/lm93.h -kernel/chips/matorb.c drivers/sensors/matorb.c -kernel/chips/max1619.c drivers/sensors/max1619.c -kernel/chips/max6650.c drivers/sensors/max6650.c -kernel/chips/maxilife.c drivers/sensors/maxilife.c -kernel/chips/mtp008.c drivers/sensors/mtp008.c -kernel/chips/pc87360.c drivers/sensors/pc87360.c -kernel/chips/pcf8574.c drivers/sensors/pcf8574.c -kernel/chips/pcf8591.c drivers/sensors/pcf8591.c -kernel/chips/sis5595.c drivers/sensors/sis5595.c -kernel/chips/smsc47m1.c drivers/sensors/smsc47m1.c -kernel/chips/thmc50.c drivers/sensors/thmc50.c -kernel/chips/via686a.c drivers/sensors/via686a.c -kernel/chips/vt1211.c drivers/sensors/vt1211.c -kernel/chips/vt8231.c drivers/sensors/vt8231.c -kernel/chips/w83781d.c drivers/sensors/w83781d.c -kernel/chips/w83792d.c drivers/sensors/w83792d.c -kernel/chips/w83627hf.c drivers/sensors/w83627hf.c -kernel/chips/w83l785ts.c drivers/sensors/w83l785ts.c -kernel/chips/xeontemp.c drivers/sensors/xeontemp.c -kernel/include/sensors_compat.h include/linux/sensors_compat.h -kernel/include/sensors_vid.h include/linux/sensors_vid.h -mkpatch/Config.in drivers/sensors/Config.in diff --git a/mkpatch/INCLUDES b/mkpatch/INCLUDES deleted file mode 100644 index 81932f14..00000000 --- a/mkpatch/INCLUDES +++ /dev/null @@ -1,2 +0,0 @@ -"sensors_compat.h" -"sensors_vid.h" diff --git a/mkpatch/Module.mk b/mkpatch/Module.mk deleted file mode 100644 index 3b3cc8e8..00000000 --- a/mkpatch/Module.mk +++ /dev/null @@ -1,26 +0,0 @@ -# Module.mk - Makefile for a Linux module for reading sensor data. -# Copyright (c) 1998, 1999 Frodo Looijaard -# -# This program is free software; you can redistribute it and/or modify -# it under the terms of the GNU General Public License as published by -# the Free Software Foundation; either version 2 of the License, or -# (at your option) any later version. -# -# This program is distributed in the hope that it will be useful, -# but WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the -# GNU General Public License for more details. -# -# You should have received a copy of the GNU General Public License -# along with this program; if not, write to the Free Software -# Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. - -# Note that MODULE_DIR (the directory in which this file resides) is a -# 'simply expanded variable'. That means that its value is substituted -# verbatim in the rules, until it is redefined. -MODULE_DIR := mkpatch -MKPATCHDIR := $(MODULE_DIR) - -clean-mkpatch: - $(RM) $(MKPATCHDIR)/.temp -clean :: clean-mkpatch diff --git a/mkpatch/mkpatch.pl b/mkpatch/mkpatch.pl deleted file mode 100755 index 2ab14c71..00000000 --- a/mkpatch/mkpatch.pl +++ /dev/null @@ -1,1341 +0,0 @@ -#!/usr/bin/perl -w - -# mkpatch - Create patches against the Linux kernel -# Copyright (C) 1999 Frodo Looijaard -# Copyright (C) 2005 Jean Delvare -# -# This program is free software; you can redistribute it and/or modify -# it under the terms of the GNU General Public License as published by -# the Free Software Foundation; either version 2 of the License, or -# (at your option) any later version. -# -# This program is distributed in the hope that it will be useful, -# but WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the -# GNU General Public License for more details. -# -# You should have received a copy of the GNU General Public License -# along with this program; if not, write to the Free Software -# Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. - -use strict; - -use vars qw($temp); -$temp = "mkpatch/.temp"; - -# Generate a diff between the old kernel file and the new lm_sensors file. We -# arrange the headers to tell us the old tree was under directory -# `linux-old', and the new tree under `linux'. -# $_[0]: sensors package root (like /tmp/sensors) -# $_[1]: Linux kernel tree (like /usr/src/linux) -# $_[2]: Name of the kernel file -# $_[3]: Name of the patched file -sub print_diff -{ - my ($package_root,$kernel_root,$kernel_file,$package_file) = @_; - my ($diff_command,$package_mtime,$kernel_mtime); - - $diff_command = "diff -u"; - if ( -e "$kernel_root/$kernel_file") { - $diff_command .= " $kernel_root/$kernel_file"; - $kernel_mtime = (stat("$kernel_root/$kernel_file"))[9]; - } else { - $diff_command .= " /dev/null"; - $kernel_mtime = 0; - } - if ( -e "$package_root/$package_file") { - $diff_command .= " $package_root/$package_file"; - $package_mtime = (stat("$package_root/$package_file"))[9]; - } else { - $diff_command .= " /dev/null"; - $package_mtime = 0; - } - open INPUT, "$diff_command|" or die "Can't execute `$diff_command'"; - if () { - ; - print "--- linux-old/$kernel_file\t".gmtime($kernel_mtime)."\n". - "+++ linux/$kernel_file\t".gmtime($package_mtime)."\n"; - - print while ; - } - close INPUT; -} - -# This generates diffs for kernel file Documentation/Configure.help. This -# file contains the help texts that can be displayed during `make *config' -# for the kernel. -# The new texts are put at the end of the file, or just before the -# lm_sensors texts. -# Of course, care is taken old lines are removed. -# $_[0]: i2c package root (like /tmp/i2c) -# $_[1]: Linux kernel tree (like /usr/src/linux) -sub gen_Documentation_Configure_help -{ - my ($package_root,$kernel_root) = @_; - my $kernel_file = "Documentation/Configure.help"; - my $package_file = $temp; - - open INPUT,"$kernel_root/$kernel_file" - or die "Can't open `$kernel_root/$kernel_file'"; - open OUTPUT,">$package_root/$package_file" - or die "Can't open $package_root/$package_file"; - MAIN: while() { - if (m@I2C mainboard interfaces@ or - m@Acer Labs ALI 1535@ or - m@Acer Labs ALI 1533 and 1543C@ or - m@Acer Labs ALI 1563@ or - m@AMD 756/766/768/8111@ or - m@SMBus multiplexing on the Tyan S4882@ or - m@AMD 8111 SMBus 2.0@ or - m@Apple Hydra Mac I/O@ or - m@Intel I801@ or - m@Intel I810/I815 based Mainboard@ or - m@Intel 82371AB PIIX4\(E\)@ or - m@Nvidia Nforce2@ or - m@Silicon Integrated Systems Corp. SiS5595 based Mainboard@ or - m@VIA Technologies, Inc. VT82C586B@ or - m@VIA Technologies, Inc. VT82C596, 596B, 686A/B, 8233@ or - m@3DFX Banshee / Voodoo3@ or - m@DEC Tsunami 21272@ or - m@Pseudo ISA adapter \(for hardware sensors modules\)@ or - m@Analog Devices ADM1021 and compatibles@ or - m@Analog Devices ADM1024@ or - m@Analog Devices ADM1025@ or - m@Analog Devices ADM1026@ or - m@Analog Devices ADM1030, ADM1031@ or - m@Analog Devices ADM9240 and compatibles@ or - m@Asus ASB100@ or - m@Dallas DS1621 and DS1625@ or - m@Fintek F71805F@ or - m@Fujitsu-Siemens Hermes@ or - m@Fujitsu-Siemens Poseidon@ or - m@Fujitsu-Siemens Scylla@ or - m@Genesys Logic GL518SM@ or - m@Genesys Logic GL520SM@ or - m@HP Maxilife@ or - m@Intel Xeon Thermal Sensor@ or - m@ITE 8705, 8712, Sis950@ or - m@Maxim MAX1619@ or - m@Maxim MAX6650, MAX6651@ or - m@Myson MTP008@ or - m@National Semiconductor LM63@ or - m@National Semiconductor LM75 and compatibles@ or - m@National Semiconductor LM78@ or - m@National Semiconductor LM80@ or - m@National Semiconductor LM83@ or - m@National Semiconductor LM85@ or - m@National Semiconductor LM87@ or - m@National Semiconductor LM90@ or - m@National Semiconductor LM92@ or - m@National Semiconductor LM93@ or - m@National Semiconductor PC8736x@ or - m@Silicon Integrated Systems Corp. SiS5595 Sensor@ or - m@Texas Instruments THMC50 / Analog Devices ADM1022@ or - m@Via VT82C686A/B@ or - m@Winbond W83781D, W83782D, W83783S@ or - m@Winbond W83792D@ or - m@Winbond W83627HF, W83627THF@ or - m@Winbond W83L785TS-S@ or - m@EEprom \(DIMM\) reader@) { - $_ = ; - $_ = ; - $_ = while not m@^\S@ and not eof(INPUT); - redo MAIN; - } - if (eof(INPUT)) { - print OUTPUT <<'EOF' -I2C mainboard interfaces -CONFIG_I2C_MAINBOARD - Many modern mainboards have some kind of I2C interface integrated. This - is often in the form of a SMBus, or System Management Bus, which is - basically the same as I2C but which uses only a subset of the I2C - protocol. - - You will also want the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -Acer Labs ALI 1535 -CONFIG_I2C_ALI1535 - If you say yes to this option, support will be included for the Acer - Labs ALI 1535 mainboard I2C interface. This can also be - built as a module. - -Acer Labs ALI 1533 and 1543C -CONFIG_I2C_ALI15X3 - If you say yes to this option, support will be included for the Acer - Labs ALI 1533 and 1543C mainboard I2C interfaces. This can also be - built as a module which can be inserted and removed while the kernel - is running. - -Acer Labs ALI 1563 -CONFIG_I2C_ALI1563 - If you say yes to this option, support will be included for the Acer - Labs ALI M1563 mainboard SMBus interface. This can also be built as a - module. - -AMD 756/766/768/8111 and nVidia nForce -CONFIG_I2C_AMD756 - If you say yes to this option, support will be included for the AMD - 756/766/768/8111 and nVidia nForce mainboard I2C interfaces. This can - also be built as a module which can be inserted and removed while the - kernel is running. - -SMBus multiplexing on the Tyan S4882 -CONFIG_I2C_AMD756_S4882 - Enabling this option will add specific SMBus support for the Tyan - S4882 motherboard. On this 4-CPU board, the SMBus is multiplexed - over 8 different channels, where the various memory module EEPROMs - and temperature sensors live. Saying yes here will give you access - to these in addition to the trunk. - -AMD 8111 SMBus 2.0 -CONFIG_I2C_AMD8111 - If you say yes to this option, support will be included for the AMD - 8111 mainboard SMBus 2.0 interface. This can also be - built as a module which can be inserted and removed while the kernel - is running. - -Apple Hydra Mac I/O -CONFIG_I2C_HYDRA - If you say yes to this option, support will be included for the - Hydra mainboard I2C interface. This can also be built as a module - which can be inserted and removed while the kernel is running. - -Intel I801 -CONFIG_I2C_I801 - If you say yes to this option, support will be included for the - Intel I801 mainboard I2C interfaces. "I810" mainboard sensor chips are - generally located on the I801's I2C bus. This can also be - built as a module which can be inserted and removed while the kernel - is running. - -Intel I810/I815 based Mainboard -CONFIG_I2C_I810 - If you say yes to this option, support will be included for the - Intel I810/I810E/I815/I845G mainboard I2C interfaces. The I2C busses - of these chips are generally used only for video devices. For "810" - mainboard sensor chips, use the I801 I2C driver instead. - - This can also be built as a module which can be inserted and removed - while the kernel is running. - -Intel 82371AB PIIX4(E), ServerWorks OSB4, CSB5, CSB6, HT-1000 -CONFIG_I2C_PIIX4 - If you say yes to this option, support will be included for the - Intel PIIX4, PIIX4E, 443MX, Serverworks OSB4, CSB5, CSB6 and - HT-1000, ATI IXP200, IXP300, IXP400 and SB600, and SMSC Victory66 - mainboard SMBus interfaces. - - This can also be built as a module which can be inserted and removed - while the kernel is running. - -Nvidia Nforce2/3/4 based Mainboard -CONFIG_I2C_NFORCE2 - If you say yes to this option, support will be included for the - Nvidia Nforce2, Nforce3 and Nforce4 families of mainboard SMBus - interfaces. - - This can also be built as a module which can be inserted and removed - while the kernel is running. - -Silicon Integrated Systems Corp. SiS5595 based Mainboard -CONFIG_I2C_SIS5595 - If you say yes to this option, support will be included for the - SiS5595 mainboard I2C interfaces. For integrated sensors on the - Sis5595, use CONFIG_SENSORS_SIS5595. This can also be - built as a module which can be inserted and removed while the kernel - is running. - -Silicon Integrated Systems Corp. SiS630/730 based Mainboard -CONFIG_I2C_SIS630 - If you say yes to this option, support will be included for the SiS 630 - and 730 mainboard I2C interfaces. This can also be built as a module - which can be inserted and removed while the kernel is running. - -Silicon Integrated Systems Corp. SiS645/961,645DX/961,735 based Mainboard -CONFIG_I2C_SIS645 - If you say yes to this option, support will be included for the SiS 645/961, - 645DX/961 and 735 mainboard I2C interfaces. This can also be built as a module - which can be inserted and removed while the kernel is running. - -VIA Technologies, Inc. VT82C586B -CONFIG_I2C_VIA - If you say yes to this option, support will be included for the VIA - Technologies I2C adapter found on some motherboards. This can also - be built as a module which can be inserted and removed while the - kernel is running. - -VIA Technologies, Inc. VT82C596/82C686/82xx and CX700 -CONFIG_I2C_VIAPRO - If you say yes to this option, support will be included for the VIA - Technologies I2C adapter on these chips. For integrated sensors on the - Via 686A/B, use CONFIG_SENSORS_VIA686A. This can also be - be built as a module which can be inserted and removed while the - kernel is running. - -3DFX Banshee / Voodoo3 -CONFIG_I2C_VOODOO3 - If you say yes to this option, support will be included for the - 3DFX Banshee and Voodoo3 I2C interfaces. The I2C busses on the these - chips are generally used only for video devices. - This can also be - built as a module which can be inserted and removed while the kernel - is running. - -DEC Tsunami 21272 -CONFIG_I2C_TSUNAMI - If you say yes to this option, support will be included for the DEC - Tsunami chipset I2C adapter. Requires the Alpha architecture; - do not enable otherwise. This can also be built as a module which - can be inserted and removed while the kernel is running. - -Pseudo ISA adapter (for hardware sensors modules) -CONFIG_I2C_ISA - This provides support for accessing some hardware sensor chips over - the ISA bus rather than the I2C or SMBus. If you want to do this, - say yes here. This feature can also be built as a module which can - be inserted and removed while the kernel is running. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -Analog Devices ADM1021 and compatibles -CONFIG_SENSORS_ADM1021 - If you say yes here you get support for Analog Devices ADM1021 - and ADM1023 sensor chips and clones: Maxim MAX1617 and MAX1617A, - Genesys Logic GL523SM, National Semi LM84, TI THMC10 and Onsemi - MC1066. This can also be built as a module which can be inserted - and removed while the kernel is running. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -Analog Devices ADM1024 -CONFIG_SENSORS_ADM1024 - If you say yes here you get support for Analog Devices ADM1024 sensor - chips. This can also be built as a module. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -Analog Devices ADM1025 -CONFIG_SENSORS_ADM1025 - If you say yes here you get support for Analog Devices ADM1025 sensor - chips. This can also be built as a module which can be inserted and - removed while the kernel is running. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -Analog Devices ADM1026 -CONFIG_SENSORS_ADM1026 - If you say yes here you get support for Analog Devices ADM1026 sensor - chips. This can also be built as a module which can be inserted and - removed while the kernel is running. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -Analog Devices ADM1030, ADM1031 -CONFIG_SENSORS_ADM1031 - If you say yes here you get support for Analog Devices ADM1030 and - ADM1031 sensor chips. This can also be built as a module which can - be inserted and removed while the kernel is running. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -Analog Devices ADM9240 and compatibles -CONFIG_SENSORS_ADM9240 - If you say yes here you get support for Analog Devices ADM9240 - sensor chips and clones: the Dallas Semiconductor DS1780 and - the National Semiconductor LM81. This can also be built as a - module which can be inserted and removed while the kernel is - running. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -Asus ASB100 -CONFIG_SENSORS_ASB100 - If you say yes here you get support for the Asus ASB100 (aka - "Bach") sensor chip. This can also be built as a module. - - You will also need the latest user-space utilities: you can find - them in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -Dallas DS1621 and DS1625 -CONFIG_SENSORS_DS1621 - If you say yes here you get support for the Dallas DS1621 and DS1625x - sensor chips. This can also be built as a module. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -Fintek F71805F -CONFIG_SENSORS_F71805F - If you say yes here you get support for the hardware monitoring - features of the Fintek F71805F/FG Super-I/O chip. This can also be - built as a module. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -Fujitsu-Siemens Hermes -CONFIG_SENSORS_FSCHER - If you say yes here you get support for the Fujitsu-Siemens Hermes - sensor chip. This can also be built as a module. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -Fujitsu-Siemens Poseidon -CONFIG_SENSORS_FSCPOS - If you say yes here you get support for the Fujitsu-Siemens Poseidon - sensor chip. This can also be built as a module. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -Fujitsu-Siemens Scylla -CONFIG_SENSORS_FSCSCY - If you say yes here you get support for the Fujitsu-Siemens Scylla - sensor chip. This can also be built as a module. This driver may/should - also work with the following Fujitsu-Siemens chips: "Poseidon", - "Poseidon II" and "Hydra". You may have to force loading of the module - for motherboards in these cases. Be careful - those motherboards have - not been tested with this driver. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -Genesys Logic GL518SM -CONFIG_SENSORS_GL518SM - If you say yes here you get support for Genesys Logic GL518SM sensor - chips. This can also be built as a module which can be inserted and - removed while the kernel is running. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -Genesys Logic GL520SM -CONFIG_SENSORS_GL520SM - If you say yes here you get support for Genesys Logic GL518SM sensor - chips. This can also be built as a module which can be inserted and - removed while the kernel is running. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -HP Maxilife -CONFIG_SENSORS_MAXILIFE - If you say yes here you get support for the HP Maxilife - sensor chip. This can also be built as a module. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -Intel Xeon Thermal Sensor -CONFIG_SENSORS_XEONTEMP - If you say yes here you get support for the Intel Xeon processor - built-in thermal sensor. This can also be built as a module which - can be inserted and removed while the kernel is running. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -ITE 8705, 8712, Sis950 -CONFIG_SENSORS_IT87 - If you say yes here you get support for the ITE 8705 and 8712 and - SiS950 sensor chips. This can also be built as a module. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -Maxim MAX1619 -CONFIG_SENSORS_MAX1619 - If you say yes here you get support for the Maxim MAX1619 sensor - chips. This can also be built as a module. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -Maxim MAX6650, MAX6651 -CONFIG_SENSORS_MAX6650 - If you say yes here you get support for the Maxim MAX6650 and - MAX6651 sensor chips. This can also be built as a module. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -Myson MTP008 -CONFIG_SENSORS_MTP008 - If you say yes here you get support for the Myson MTP008 - sensor chip. This can also be built as a module. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -National Semiconductor LM63 -CONFIG_SENSORS_LM63 - If you say yes here you get support for National Semiconductor LM63 - sensor chips. This can also be built as a module which can be inserted - and removed while the kernel is running. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -National Semiconductor LM75 and compatibles -CONFIG_SENSORS_LM75 - If you say yes here you get support for National Semiconductor LM75 - sensor chips and clones: Dallas Semiconductor DS75 and DS1775 (in - 9-bit precision mode), and TelCom (now Microchip) TCN75. This can - also be built as a module which can be inserted and removed while - the kernel is running. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -National Semiconductor LM78 -CONFIG_SENSORS_LM78 - If you say yes here you get support for National Semiconductor LM78 - sensor chips family: the LM78-J and LM79. Many clone chips will - also work at least somewhat with this driver. This can also be built - as a module which can be inserted and removed while the kernel is - running. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -National Semiconductor LM80 -CONFIG_SENSORS_LM80 - If you say yes here you get support for National Semiconductor LM80 - sensor chips. This can also be built as a module which can be - inserted and removed while the kernel is running. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -National Semiconductor LM83 and compatibles -CONFIG_SENSORS_LM83 - If you say yes here you get support for the National Semiconductor - LM82 and LM83 sensor chips. This can also be built as a module. - - You will also need the latest user-space utilities: you can find - them in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -National Semiconductor LM85 -CONFIG_SENSORS_LM85 - If you say yes here you get support for National Semiconductor LM85 - sensor chips and compatibles. Compatible chips include the Analog - Devices ADM1027 and ADT7463 and SMSC EMC6D100 and EMC6D101. This - can also be built as a module which can be inserted and removed - while the kernel is running. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -National Semiconductor LM87 -CONFIG_SENSORS_LM87 - If you say yes here you get support for National Semiconductor LM87 - sensor chips. This can also be built as a module which can be - inserted and removed while the kernel is running. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -National Semiconductor LM90 -CONFIG_SENSORS_LM90 - If you say yes here you get support for the National Semiconductor - LM90, LM89 and LM99, Analog Devices ADM1032 and ADT7461, and Maxim - MAX6657 and MAX6658 sensor chips. This can also be built as a module. - - You will also need the latest user-space utilities: you can find - them in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -National Semiconductor LM92 -CONFIG_SENSORS_LM92 - If you say yes here you get support for National Semiconductor LM92 - sensor chips. This can also be built as a module which can be - inserted and removed while the kernel is running. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -National Semiconductor LM93 -CONFIG_SENSORS_LM93 - If you say yes here you get support for National Semiconductor LM93 - sensor chips. This can also be built as a module which can be inserted - and removed while the kernel is running. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -National Semiconductor PC8736x Sensors -CONFIG_SENSORS_PC87360 - If you say yes here you get support for the integrated hardware - monitoring in the National Semicoductor PC87360, PC87363, PC87364, - PC87365 and PC87366 Super I/O chips. This can also be built as a - module which can be inserted and removed while the kernel is - running. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -Philips PCF8574 -CONFIG_SENSORS_PCF8574 - If you say yes here you get support for the Philips PCF8574 - I2C 8-bit Parallel I/O device. - This can also be built as a module which can be - inserted and removed while the kernel is running. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -Philips PCF8591 -CONFIG_SENSORS_PCF8591 - If you say yes here you get support for the Philips PCF8591 - I2C Quad D/A + Single A/D I/O device. - This can also be built as a module which can be - inserted and removed while the kernel is running. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -Silicon Integrated Systems Corp. SiS5595 Sensor -CONFIG_SENSORS_SIS5595 - If you say yes here you get support for the integrated sensors in - SiS5595 South Bridges. This can also be built as a module - which can be inserted and removed while the kernel is running. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -SMSC47M1xx Super I/O Fan Support -CONFIG_SENSORS_SMSC47M1 - If you say yes here you get support for the integrated fan - monitoring and control in the SMSC 47M1xx Super I/O chips. - This can also be built as a module - which can be inserted and removed while the kernel is running. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -Texas Instruments THMC50 / Analog Devices ADM1022 -CONFIG_SENSORS_THMC50 - If you say yes here you get support for Texas Instruments THMC50 - sensor chips and clones: the Analog Devices ADM1022. - This can also be built as a module which - can be inserted and removed while the kernel is running. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -Via VT82C686A/B -CONFIG_SENSORS_VIA686A - If you say yes here you get support for the integrated sensors in - Via 686A/B South Bridges. This can also be built as a module - which can be inserted and removed while the kernel is running. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -Via VT1211 Sensors -CONFIG_SENSORS_VT1211 - If you say yes here you get support for the integrated sensors in - the Via VT1211 Super I/O device. This can also be built as a module - which can be inserted and removed while the kernel is running. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -Via VT8231 Sensors -CONFIG_SENSORS_VT8231 - If you say yes here you get support for the integrated sensors in - the Via VT8231 device. This can also be built as a module - which can be inserted and removed while the kernel is running. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -Winbond W83781D, W83782D, W83783S, W83627HF, AS99127F -CONFIG_SENSORS_W83781D - If you say yes here you get support for the Winbond W8378x series - of sensor chips: the W83781D, W83782D, W83783S and W83627HF, - and the similar Asus AS99127F. This can also be built as a module - which can be inserted and removed while the kernel is running. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -Winbond W83792D -CONFIG_SENSORS_W83792D - If you say yes here you get support for the Winbond W83792D - sensor chips. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -Winbond W83627HF, W83627THF, W83637HF, W83687THF, W83697HF -CONFIG_SENSORS_W83627HF - If you say yes here you get support for the Winbond W836x7 series - of sensor chips: the W83627HF, W83627THF, W83637HF, W83687THF and - W83697HF. This can also be built as a module which can be inserted - and removed while the kernel is running. - - You will also need the latest user-space utilities: you can find - them in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -Winbond W83L785TS-S -CONFIG_SENSORS_W83L785TS - If you say yes here you get support for the Winbond W83L785TS-S - sensor chip. This can also be built as a module. - - You will also need the latest user-space utilities: you can find - them in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -EEprom (DIMM) reader -CONFIG_SENSORS_EEPROM - If you say yes here you get read-only access to the EEPROM data - available on modern memory DIMMs, and which could theoretically - also be available on other devices. This can also be built as a - module which can be inserted and removed while the kernel is - running. - - You will also need the latest user-space utilities: you can find them - in the lm_sensors package, which you can download at - http://www.lm-sensors.org/ - -EOF - } - print OUTPUT; - } - close INPUT; - close OUTPUT; - print_diff $package_root,$kernel_root,$kernel_file,$package_file; -} - - -# This generates diffs for the main Linux Makefile. -# Three lines which add drivers/sensors/sensors.a to the DRIVERS list are -# put just before the place where the architecture Makefile is included. -# Of course, care is taken old lines are removed. -# $_[0]: sensors package root (like /tmp/sensors) -# $_[1]: Linux kernel tree (like /usr/src/linux) -sub gen_Makefile -{ - my ($package_root,$kernel_root) = @_; - my $kernel_file = "Makefile"; - my $package_file = $temp; - my $type = 0; - my $pr1 = 0; - - open INPUT,"$kernel_root/$kernel_file" - or die "Can't open `$kernel_root/$kernel_file'"; - open OUTPUT,">$package_root/$package_file" - or die "Can't open $package_root/$package_file"; - `grep -q -s 'i2c\.o' "$kernel_root/$kernel_file"`; - $type = 2 if ! $?; - MAIN: while() { - $type = 1 if !$type and (m@^DRIVERS-\$@); - if (m@DRIVERS-\$\(CONFIG_SENSORS\)@) { - $_ = ; - redo MAIN; - } elsif (m@CONFIG_SENSORS@) { - $_ = while not m@endif@; - $_ = ; - $_ = if m@^$@; - redo MAIN; - } - if ($type == 1 and m@^DRIVERS \+= \$\(DRIVERS-y\)@) { - print OUTPUT <<'EOF'; -DRIVERS-$(CONFIG_SENSORS) += drivers/sensors/sensors.a -EOF - $pr1 = 1; - } - if ($type == 2 and m@^DRIVERS .*= \$\(DRIVERS-y\)@) { - print OUTPUT <<'EOF'; -DRIVERS-$(CONFIG_SENSORS) += drivers/sensors/sensor.o -EOF - $pr1 = 1; - } - if ($type == 0 and m@include arch/\$\(ARCH\)/Makefile@) { - print OUTPUT <<'EOF'; -ifeq ($(CONFIG_SENSORS),y) -DRIVERS := $(DRIVERS) drivers/sensors/sensors.a -endif - -EOF - $pr1 = 1; - } - print OUTPUT; - } - close INPUT; - close OUTPUT; - die "Automatic patch generation for main `Makefile' failed.\n". - "See our home page http://www.lm-sensors.org/ for assistance!" if $pr1 == 0; - print_diff $package_root,$kernel_root,$kernel_file,$package_file; -} - -# This generates diffs for drivers/Makefile -# First, `sensors' is added to the ALL_SUB_DIRS list. Next, a couple of lines -# to add sensors to the SUB_DIRS and/or MOD_SUB_DIRS lists is put right before -# Rules.make is included. -# Of course, care is taken old lines are removed. -# $_[0]: sensors package root (like /tmp/sensors) -# $_[1]: Linux kernel tree (like /usr/src/linux) -sub gen_drivers_Makefile -{ - my ($package_root,$kernel_root) = @_; - my $kernel_file = "drivers/Makefile"; - my $package_file = $temp; - my $sensors_present; - my $pr1 = 0; - my $pr2 = 0; - my $new_style = 0; - - open INPUT,"$kernel_root/$kernel_file" - or die "Can't open `$kernel_root/$kernel_file'"; - open OUTPUT,">$package_root/$package_file" - or die "Can't open $package_root/$package_file"; - MAIN: while() { - if (m@^mod-subdirs\s*:=@) { - $new_style = 1; - } - if ((! $new_style and m@^ALL_SUB_DIRS\s*:=@) or m@^mod-subdirs\s*:=@) { - $pr1 = 1; - $sensors_present = 0; - while (m@\\$@) { - $sensors_present = 1 if m@sensors@; - print OUTPUT; - $_ = ; - } - $sensors_present = 1 if m@sensors@; - s@$@ sensors@ if (not $sensors_present); - print OUTPUT; - $_ = ; - redo MAIN; - } - if (m@^ifeq.*CONFIG_SENSORS@) { - $_ = while not m@^endif@; - $_ = ; - $_ = if m@^$@; - redo MAIN; - } - if (m@^subdir.*CONFIG_SENSORS@) { - $_ = ; - redo MAIN; - } - if (!$pr2 and (m@^include \$\(TOPDIR\)/Rules.make$@ or m@^subdir-\$\(CONFIG_ACPI@)) { - $pr2 = 1; - if ($new_style) { - print OUTPUT <<'EOF'; -subdir-$(CONFIG_SENSORS) += sensors -EOF - } else { - print OUTPUT <<'EOF'; -ifeq ($(CONFIG_SENSORS),y) -SUB_DIRS += sensors -MOD_SUB_DIRS += sensors -else - ifeq ($(CONFIG_SENSORS),m) - MOD_SUB_DIRS += sensors - endif -endif - -EOF - } - } - print OUTPUT; - } - close INPUT; - close OUTPUT; - die "Automatic patch generation for `drivers/Makefile' failed.\n". - "See our home page http://www.lm-sensors.org/ for assistance!" if $pr1 == 0 or $pr2 == 0; - print_diff $package_root,$kernel_root,$kernel_file,$package_file; -} - -# This generates diffs for drivers/char/Config.in -# It adds a line just before CONFIG_APM or main_menu_option lines to include -# the sensors Config.in. -# Of course, care is taken old lines are removed. -# $_[0]: sensors package root (like /tmp/sensors) -# $_[1]: Linux kernel tree (like /usr/src/linux) -sub gen_drivers_char_Config_in -{ - my ($package_root,$kernel_root) = @_; - my $kernel_file = "drivers/char/Config.in"; - my $package_file = $temp; - my $pr1 = 0; - - open INPUT,"$kernel_root/$kernel_file" - or die "Can't open `$kernel_root/$kernel_file'"; - open OUTPUT,">$package_root/$package_file" - or die "Can't open $package_root/$package_file"; - MAIN: while() { - if (m@source drivers/i2c/Config.in@) { - $pr1 = 1; - print OUTPUT; - print OUTPUT "\nsource drivers/sensors/Config.in\n"; - $_ = ; - redo MAIN; - } - if (m@sensors@) { - $_ = ; - $_ = if m@^$@; - redo MAIN; - } - print OUTPUT; - } - close INPUT; - close OUTPUT; - die "Automatic patch generation for `drivers/char/Config.in' failed.\n". - "See our home page http://www.lm-sensors.org/ for assistance!" if $pr1 == 0; - print_diff $package_root,$kernel_root,$kernel_file,$package_file; -} - -# This generates diffs for drivers/i2c/Config.in -# Several adapter drivers that are included in the lm_sensors package are -# added at the first and onlu sensors marker. -# Of course, care is taken old lines are removed. -# $_[0]: sensors package root (like /tmp/sensors) -# $_[1]: Linux kernel tree (like /usr/src/linux) -sub gen_drivers_i2c_Config_in -{ - my ($package_root,$kernel_root) = @_; - my $kernel_file = "drivers/i2c/Config.in"; - my $package_file = "$temp"; - my $pr1 = 0; - - open INPUT,"$kernel_root/$kernel_file" - or die "Can't open `$kernel_root/$kernel_file'"; - open OUTPUT,">$package_root/$package_file" - or die "Can't open $package_root/$package_file"; - while() { - if (m@sensors code starts here@) { - $pr1++; - print OUTPUT; - while () { - last if m@sensors code ends here@; - } - print OUTPUT << 'EOF'; - bool 'I2C mainboard interfaces' CONFIG_I2C_MAINBOARD - if [ "$CONFIG_I2C_MAINBOARD" = "y" ]; then - dep_tristate ' Acer Labs ALI 1535' CONFIG_I2C_ALI1535 $CONFIG_I2C - dep_tristate ' Acer Labs ALI 1533 and 1543C' CONFIG_I2C_ALI15X3 $CONFIG_I2C - dep_tristate ' Acer Labs ALI 1563' CONFIG_I2C_ALI1563 $CONFIG_I2C - dep_tristate ' Apple Hydra Mac I/O' CONFIG_I2C_HYDRA $CONFIG_I2C_ALGOBIT - dep_tristate ' AMD 756/766/768/8111 and nVidia nForce' CONFIG_I2C_AMD756 $CONFIG_I2C - if [ "$CONFIG_I2C_AMD756" != "n" ]; then - dep_tristate ' SMBus multiplexing on the Tyan S4882' CONFIG_I2C_AMD756_S4882 $CONFIG_I2C_AMD756 - fi - dep_tristate ' AMD 8111 SMBus 2.0' CONFIG_I2C_AMD8111 $CONFIG_I2C - if [ "$CONFIG_ALPHA" = "y" ]; then - dep_tristate ' DEC Tsunami I2C interface' CONFIG_I2C_TSUNAMI $CONFIG_I2C_ALGOBIT - fi - dep_tristate ' Intel 82801 (ICH) and ESB' CONFIG_I2C_I801 $CONFIG_I2C - dep_tristate ' Intel i810AA/AB/E and i815' CONFIG_I2C_I810 $CONFIG_I2C_ALGOBIT - dep_tristate ' Intel 82371AB PIIX4(E), 443MX, ServerWorks OSB4/CSB5, SMSC Victory66' CONFIG_I2C_PIIX4 $CONFIG_I2C - dep_tristate ' Nvidia Nforce2/3/4' CONFIG_I2C_NFORCE2 $CONFIG_I2C - dep_tristate ' SiS 5595' CONFIG_I2C_SIS5595 $CONFIG_I2C - dep_tristate ' SiS 630/730' CONFIG_I2C_SIS630 $CONFIG_I2C - dep_tristate ' SiS 645/961,645DX/961,735' CONFIG_I2C_SIS645 $CONFIG_I2C $CONFIG_HOTPLUG - dep_tristate ' Savage 4' CONFIG_I2C_SAVAGE4 $CONFIG_I2C_ALGOBIT - dep_tristate ' VIA Technologies, Inc. VT82C586B' CONFIG_I2C_VIA $CONFIG_I2C_ALGOBIT - dep_tristate ' VIA Technologies, Inc. VT82C596/82C686/82xx and CX700' CONFIG_I2C_VIAPRO $CONFIG_I2C - dep_tristate ' Voodoo3 I2C interface' CONFIG_I2C_VOODOO3 $CONFIG_I2C_ALGOBIT - dep_tristate ' Pseudo ISA adapter (for some hardware sensors)' CONFIG_I2C_ISA $CONFIG_I2C - fi - -EOF - } - print OUTPUT; - } - close INPUT; - close OUTPUT; - die "Automatic patch generation for `drivers/i2c/Config.in' failed.\n". - "See our home page http://www.lm-sensors.org/ for assistance!" if $pr1 != 1; - print_diff $package_root,$kernel_root,$kernel_file,$package_file; -} - -sub gen_drivers_sensors_Makefile -{ - my ($package_root,$kernel_root) = @_; - my $kernel_file = "drivers/sensors/Makefile"; - my $package_file = $temp; - - open OUTPUT,">$package_root/$package_file" - or die "Can't open $package_root/$package_file"; - print OUTPUT <<'EOF'; -# -# Makefile for the kernel hardware sensors drivers. -# - -MOD_LIST_NAME := SENSORS_MODULES -O_TARGET := sensor.o - -obj-$(CONFIG_SENSORS_ADM1021) += adm1021.o -obj-$(CONFIG_SENSORS_ADM1024) += adm1024.o -obj-$(CONFIG_SENSORS_ADM1025) += adm1025.o -obj-$(CONFIG_SENSORS_ADM1026) += adm1026.o -obj-$(CONFIG_SENSORS_ADM1031) += adm1031.o -obj-$(CONFIG_SENSORS_ADM9240) += adm9240.o -obj-$(CONFIG_SENSORS_ASB100) += asb100.o -obj-$(CONFIG_SENSORS_BT869) += bt869.o -obj-$(CONFIG_SENSORS_DDCMON) += ddcmon.o -obj-$(CONFIG_SENSORS_DS1621) += ds1621.o -obj-$(CONFIG_SENSORS_EEPROM) += eeprom.o -obj-$(CONFIG_SENSORS_F71805F) += f71805f.o -obj-$(CONFIG_SENSORS_FSCHER) += fscher.o -obj-$(CONFIG_SENSORS_FSCPOS) += fscpos.o -obj-$(CONFIG_SENSORS_FSCSCY) += fscscy.o -obj-$(CONFIG_SENSORS_GL518SM) += gl518sm.o -obj-$(CONFIG_SENSORS_GL520SM) += gl520sm.o -obj-$(CONFIG_SENSORS_IT87) += it87.o -obj-$(CONFIG_SENSORS_LM63) += lm63.o -obj-$(CONFIG_SENSORS_LM75) += lm75.o -obj-$(CONFIG_SENSORS_LM78) += lm78.o -obj-$(CONFIG_SENSORS_LM80) += lm80.o -obj-$(CONFIG_SENSORS_LM83) += lm83.o -obj-$(CONFIG_SENSORS_LM85) += lm85.o -obj-$(CONFIG_SENSORS_LM87) += lm87.o -obj-$(CONFIG_SENSORS_LM90) += lm90.o -obj-$(CONFIG_SENSORS_LM92) += lm92.o -obj-$(CONFIG_SENSORS_LM93) += lm93.o -obj-$(CONFIG_SENSORS_MAX1619) += max1619.o -obj-$(CONFIG_SENSORS_MAX6650) += max6650.o -obj-$(CONFIG_SENSORS_MAXILIFE) += maxilife.o -obj-$(CONFIG_SENSORS_MTP008) += mtp008.o -obj-$(CONFIG_SENSORS_PC87360) += pc87360.o -obj-$(CONFIG_SENSORS_PCF8574) += pcf8574.o -obj-$(CONFIG_SENSORS_PCF8591) += pcf8591.o -obj-$(CONFIG_SENSORS_SIS5595) += sis5595.o -obj-$(CONFIG_SENSORS_SMSC47M1) += smsc47m1.o -obj-$(CONFIG_SENSORS_THMC50) += thmc50.o -obj-$(CONFIG_SENSORS_VIA686A) += via686a.o -obj-$(CONFIG_SENSORS_VT1211) += vt1211.o -obj-$(CONFIG_SENSORS_VT8231) += vt8231.o -obj-$(CONFIG_SENSORS_W83781D) += w83781d.o -obj-$(CONFIG_SENSORS_W83792D) += w83792d.o -obj-$(CONFIG_SENSORS_W83627HF) += w83627hf.o -obj-$(CONFIG_SENSORS_W83L785TS) += w83l785ts.o -obj-$(CONFIG_SENSORS_XEONTEMP) += xeontemp.o - -include $(TOPDIR)/Rules.make - -EOF - close OUTPUT; - print_diff $package_root,$kernel_root,$kernel_file,$package_file; -} - -# This generates diffs for drivers/i2c/Makefile. -# Lines to add correct files to M_OBJS and/or L_OBJS are added just before -# Rules.make is included -# Of course, care is taken old lines are removed. -# $_[0]: sensors package root (like /tmp/sensors) -# $_[1]: Linux kernel tree (like /usr/src/linux) -sub gen_drivers_i2c_Makefile -{ - my ($package_root,$kernel_root) = @_; - my $kernel_file = "drivers/i2c/Makefile"; - my $package_file = $temp; - my $pr1 = 0; - - open INPUT,"$kernel_root/$kernel_file" - or die "Can't open `$kernel_root/$kernel_file'"; - open OUTPUT,">$package_root/$package_file" - or die "Can't open $package_root/$package_file"; - while() { - if (m@sensors code starts here@) { - $pr1 ++; - print OUTPUT; - while () { - last if m@sensors code ends here@; - } - print OUTPUT <<'EOF'; -export-objs += i2c-amd756.o - -obj-$(CONFIG_I2C_ALI1535) += i2c-ali1535.o -obj-$(CONFIG_I2C_ALI15X3) += i2c-ali15x3.o -obj-$(CONFIG_I2C_ALI1563) += i2c-ali1563.o -obj-$(CONFIG_I2C_AMD756) += i2c-amd756.o -obj-$(CONFIG_I2C_AMD756_S4882) += i2c-amd756-s4882.o -obj-$(CONFIG_I2C_AMD8111) += i2c-amd8111.o -obj-$(CONFIG_I2C_HYDRA) += i2c-hydra.o -obj-$(CONFIG_I2C_I801) += i2c-i801.o -obj-$(CONFIG_I2C_I810) += i2c-i810.o -obj-$(CONFIG_I2C_ISA) += i2c-isa.o -obj-$(CONFIG_I2C_NFORCE2) += i2c-nforce2.o -obj-$(CONFIG_I2C_PIIX4) += i2c-piix4.o -obj-$(CONFIG_I2C_SIS5595) += i2c-sis5595.o -obj-$(CONFIG_I2C_SIS630) += i2c-sis630.o -obj-$(CONFIG_I2C_SIS645) += i2c-sis645.o -obj-$(CONFIG_I2C_SAVAGE4) += i2c-savage4.o -obj-$(CONFIG_I2C_TSUNAMI) += i2c-tsunami.o -obj-$(CONFIG_I2C_VIA) += i2c-via.o -obj-$(CONFIG_I2C_VIAPRO) += i2c-viapro.o -obj-$(CONFIG_I2C_VOODOO3) += i2c-voodoo3.o -EOF - } - print OUTPUT; - } - close INPUT; - close OUTPUT; - die "Automatic patch generation for `drivers/i2c/Makefile' failed.\n". - "See our home page http://www.lm-sensors.org/ for assistance!" if $pr1 != 1; - print_diff $package_root,$kernel_root,$kernel_file,$package_file; -} - -# Generate the diffs for the list of MAINTAINERS -# $_[0]: i2c package root (like /tmp/i2c) -# $_[1]: Linux kernel tree (like /usr/src/linux) -sub gen_MAINTAINERS -{ - my ($package_root,$kernel_root) = @_; - my $kernel_file = "MAINTAINERS"; - my $package_file = $temp; - my $done = 0; - - open INPUT,"$kernel_root/$kernel_file" - or die "Can't open `$kernel_root/$kernel_file'"; - open OUTPUT,">$package_root/$package_file" - or die "Can't open $package_root/$package_file"; - MAIN: while() { - if (m@SENSORS DRIVERS@) { - $_= while not m@^$@; - $_=; - redo MAIN; - } - if (not $done and (m@SGI VISUAL WORKSTATION 320 AND 540@)) { - print OUTPUT <<'EOF'; -SENSORS DRIVERS -L: lm-sensors@lm-sensors.org -W: http://www.lm-sensors.org/ -S: Maintained - -EOF - $done = 1; - } - print OUTPUT; - } - close INPUT; - close OUTPUT; - die "Automatic patch generation for `MAINTAINERS' failed.\n". - "See our home page http://www.lm-sensors.org/ for assistance!" if $done == 0; - print_diff $package_root,$kernel_root,$kernel_file,$package_file; -} - -# Generate the diffs for dmi_scan.c and i386_ksyms.c -# $_[0]: i2c package root (like /tmp/i2c) -# $_[1]: Linux kernel tree (like /usr/src/linux) -sub gen_dmi_scan -{ - my ($package_root,$kernel_root) = @_; - my $kernel_file = "arch/i386/kernel/dmi_scan.c"; - my $package_file = $temp; - my $done = 0; - - open INPUT,"$kernel_root/$kernel_file" - or die "Can't open `$kernel_root/$kernel_file'"; - open OUTPUT,">$package_root/$package_file" - or die "Can't open $package_root/$package_file"; - MAIN: while() { - if ($done == 0 && m/^\s*int is_sony_vaio_laptop;\s*$/) { - print OUTPUT <<'EOF'; -int is_unsafe_smbus; -EOF - $done++; - } - if ($done == 1 && m/^\s*\* Check for a Sony Vaio system\s*$/) { - print OUTPUT <<'EOF'; - * Don't access SMBus on IBM systems which get corrupted eeproms - */ - -static __init int disable_smbus(struct dmi_blacklist *d) -{ - if (is_unsafe_smbus == 0) { - is_unsafe_smbus = 1; - printk(KERN_INFO "%s machine detected. Disabling SMBus accesses.\n", d->ident); - } - return 0; -} - -/* -EOF - $done++; - } - if ($done == 2 && m/^\s*\{ sony_vaio_laptop, "Sony Vaio", \{ \/\* This is a Sony Vaio laptop \*\/\s*$/) { - print OUTPUT <<'EOF'; - { disable_smbus, "IBM", { - MATCH(DMI_SYS_VENDOR, "IBM"), - NO_MATCH, NO_MATCH, NO_MATCH - } }, -EOF - $done++; - } - print OUTPUT; - } - close INPUT; - close OUTPUT; - die "Automatic patch generation for `$kernel_file' failed.\n". - "See our home page http://www.lm-sensors.org/ for assistance!" if $done != 3; - print_diff $package_root,$kernel_root,$kernel_file,$package_file; - - $kernel_file = "arch/i386/kernel/i386_ksyms.c"; - $done = 0; - - open INPUT,"$kernel_root/$kernel_file" - or die "Can't open `$kernel_root/$kernel_file'"; - open OUTPUT,">$package_root/$package_file" - or die "Can't open $package_root/$package_file"; - MAIN: while() { - if ($done == 0 && m/^\s*extern int is_sony_vaio_laptop;\s*$/) { - print OUTPUT <<'EOF'; -extern int is_unsafe_smbus; -EXPORT_SYMBOL(is_unsafe_smbus); - -EOF - $done++; - } - print OUTPUT; - } - close INPUT; - close OUTPUT; - die "Automatic patch generation for `$kernel_file' failed.\n". - "See our home page http://www.lm-sensors.org/ for assistance!" if $done != 1; - print_diff $package_root,$kernel_root,$kernel_file,$package_file; -} - - -sub usage -{ - print "Usage: $0 package_root kernel_root\n"; - exit 1; -} - -# Main function -sub main -{ - my ($package_root,$kernel_root,%files,%includes,$package_file,$kernel_file); - my ($diff_command,$dummy,$data0,$data1,$sedscript,$version_string); - - # --> Read the command-line - $package_root = $ARGV[0]; - usage() unless defined $package_root; - die "Package root `$package_root' is not found\n" - unless -d "$package_root/mkpatch"; - $kernel_root = $ARGV[1]; - usage() unless defined $kernel_root; - die "Kernel root `$kernel_root' is not found\n" - unless -f "$kernel_root/Rules.make"; - - # --> Read FILES - open INPUT, "$package_root/mkpatch/FILES" - or die "Can't open `$package_root/mkpatch/FILES'"; - while () { - ($data0,$data1) = /(\S+)\s+(\S+)/; - $files{$data0} = $data1; - } - close INPUT; - - # --> Read INCLUDES - open INPUT, "$package_root/mkpatch/INCLUDES" - or die "Can't open `$package_root/mkpatch/INCLUDES'"; - while () { - ($data0,$data1) = /(\S+)\s+(\S+)/; - $includes{$data0} = $data1; - $sedscript .= 's,(#\s*include\s*)'.$data0.'(\s*),$1'."$data1".'$2, ; '; - } - close INPUT; - - die "First apply the i2c patches to `$kernel_root'!" - if ! -d "$kernel_root/drivers/i2c"; - - # --> Read "version.h" - open INPUT, "$package_root/version.h" - or die "Can't open `$package_root/version.h'"; - $version_string .= $_ while ; - close INPUT; - - # --> Start generating - foreach $package_file (sort keys %files) { - open INPUT,"$package_root/$package_file" - or die "Can't open `$package_root/$package_file'"; - open OUTPUT,">$package_root/$temp" - or die "Can't open `$package_root/$temp'"; - while () { - eval $sedscript; - if (m@#\s*include\s*"version.h"@) { - print OUTPUT $version_string; - } else { - print OUTPUT; - } - } - close INPUT; - close OUTPUT; - - $kernel_file = $files{$package_file}; - print_diff $package_root,$kernel_root,$kernel_file,$temp; - } - - gen_Makefile $package_root, $kernel_root; - gen_drivers_Makefile $package_root, $kernel_root; - gen_drivers_sensors_Makefile $package_root, $kernel_root; - gen_drivers_char_Config_in $package_root, $kernel_root; - gen_drivers_i2c_Config_in $package_root, $kernel_root; - gen_drivers_i2c_Makefile $package_root, $kernel_root; - gen_Documentation_Configure_help $package_root, $kernel_root; - gen_MAINTAINERS $package_root, $kernel_root; - gen_dmi_scan $package_root, $kernel_root; - - # Clear temporary file - unlink("$package_root/$temp"); -} - -main; -