wt/lm-sensors
1
0 Fork 0
mirror of https://github.com/lm-sensors/lm-sensors.git synced 2026-11-11 16:40:16 +00:00
Code Issues Packages Projects Releases Wiki Activity

Delete mkpatch and all references thereto. The kernel modules will soon

Browse Source 
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
This commit is contained in:
Jean Delvare committed 2007-05-02 10:35:14 +00:00
1 parent 1d4796cfbc
commit 95996b4638
13 files changed
+13 -1729
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

CHANGES
+1
View File
@@ -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
INSTALL
+11 -104
View File
@@ -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
=========================
Makefile
-1
View File
@@ -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
README.directories
-2
View File
@@ -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.
doc/developers/new_drivers
+1 -26
View File
@@ -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)
doc/mkpatch
-82
View File
@@ -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 <linux/sensors.h>' 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
kernel/busses/Module.mk
-2
View File
@@ -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
kernel/chips/Module.mk
-2
View File
@@ -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
mkpatch/Config.in
-69
View File
@@ -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
mkpatch/FILES
-72
View File
@@ -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
mkpatch/INCLUDES
-2
View File
@@ -1,2 +0,0 @@
"sensors_compat.h" <linux/sensors_compat.h>
"sensors_vid.h" <linux/sensors_vid.h>
mkpatch/Module.mk
-26
View File
@@ -1,26 +0,0 @@
# Module.mk - Makefile for a Linux module for reading sensor data.
# Copyright (c) 1998, 1999 Frodo Looijaard <frodol@dds.nl>
#
# 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
mkpatch/mkpatch.pl
-1341
View File
File diff suppressed because it is too large. Load diff