| 1 | This is a list of modules, the modules they depend on, and the module |
|---|
| 2 | parameters they define. First, some things about managing all these |
|---|
| 3 | modules. |
|---|
| 4 | |
|---|
| 5 | The hardcore way is to insmod each of them by hand. This is not very |
|---|
| 6 | practical, though. It is better to install them in a subdirectory that |
|---|
| 7 | modprobe examines. /lib/modules/current/extra/misc comes to mind. |
|---|
| 8 | You need to add this path to your /etc/modules.conf (or /etc/conf.modules, |
|---|
| 9 | which file is used depends on your distribution): |
|---|
| 10 | (modules-2.0.0): |
|---|
| 11 | path[misc]=/lib/modules/current/extra/misc |
|---|
| 12 | (modutils-2.1.x): |
|---|
| 13 | path=/lib/modules/current/extra |
|---|
| 14 | Do always a 'killall -HUP kerneld; depmod -a' after changing either your |
|---|
| 15 | configuration file or changing a module in one of the module directories. |
|---|
| 16 | |
|---|
| 17 | Now you can do 'modprobe lm78', and all dependent modules are loaded |
|---|
| 18 | automatically. You could, of course, add this statement (and related |
|---|
| 19 | statements for other drivers) somewhere in your rc files. But, most |
|---|
| 20 | distributions are set up to load automatically all files in the |
|---|
| 21 | 'boot' directories on system start, so why not use this? The best |
|---|
| 22 | way to do this is to create directory /lib/modules/boot, and to |
|---|
| 23 | put *links* to the real modules in there. Why links? Well, by linking |
|---|
| 24 | to /lib/modules/current/whatever, this will function for any kernel |
|---|
| 25 | (provided /lib/modules/current is correctly set up to point to the |
|---|
| 26 | current kernel). So: |
|---|
| 27 | mkdir -p /lib/modules/boot |
|---|
| 28 | ln -s ../current/extra/misc/lm78.o /lib/modules/boot/lm78.o |
|---|
| 29 | # etc. |
|---|
| 30 | |
|---|
| 31 | It is also possible to specify default options, that you would normally |
|---|
| 32 | enter at the insmod command, in the configuration file. The syntax is |
|---|
| 33 | as follows: |
|---|
| 34 | options i2c-core debug=2 |
|---|
| 35 | |
|---|
| 36 | With the above, the managing of all those modules is suddenly no problem |
|---|
| 37 | at all! |
|---|
| 38 | |
|---|
| 39 | |
|---|
| 40 | (i2c) i2c-core: |
|---|
| 41 | The core i2c module (surprise!). Almost everything else depends on this one. |
|---|
| 42 | Module parameters: |
|---|
| 43 | i2c_debug (i) Set debug level |
|---|
| 44 | |
|---|
| 45 | (src) i2c-proc: i2c-core |
|---|
| 46 | Creates /proc/bus/i2c* files. |
|---|
| 47 | |
|---|
| 48 | (src) smbus: i2c-core |
|---|
| 49 | SMBus emulation on i2c busses. Base algorithm, on which SMBus-only adapters |
|---|
| 50 | rely. |
|---|
| 51 | |
|---|
| 52 | (src) piix4: smbus i2c-core |
|---|
| 53 | PIIX4 SMBus access. |
|---|
| 54 | |
|---|
| 55 | (src) isa: i2c-core |
|---|
| 56 | Defines the ISA bus as being a I2C adapter. It isn't, of course; but this is |
|---|
| 57 | often used by sensor client modules, to keep the code small and simple. |
|---|
| 58 | |
|---|
| 59 | (src) sensors: i2c-core |
|---|
| 60 | General purpose routines for sensor client modules |
|---|
| 61 | |
|---|
| 62 | (src) lm78: sensors smbus i2c-core |
|---|
| 63 | LM78, LM78-J and LM79 chip driver |
|---|
| 64 | |
|---|
| 65 | (src) lm75: sensors smbus i2c-core |
|---|
| 66 | LM75 chip driver |
|---|
| 67 | |
|---|
| 68 | (src) gl518sm: sensors smbus i2c-core |
|---|
| 69 | GL518SM revision 0x00 and 0x80 chip driver |
|---|
| 70 | |
|---|
| 71 | (i2c) algo-bit: i2c-core |
|---|
| 72 | The 'bit' algorithm, used by many i2c adapters |
|---|
| 73 | Module parameters: |
|---|
| 74 | bit_test (i) Test the lines of the bus to see if it is stuck |
|---|
| 75 | bit_scan (i) Scan for active chips on the bus |
|---|
| 76 | i2c_debug (i) debug level - 0 off; 1 normal; 2,3 more verbose; |
|---|
| 77 | 9 bit-protocol |
|---|
| 78 | |
|---|
| 79 | (i2c) bit-mb: algo-bit i2c-core |
|---|
| 80 | VIA VT82C586B bus access. This is often used instead of the PIIX4 as SMBus |
|---|
| 81 | host. |
|---|
| 82 | |
|---|
| 83 | (i2c) bit-lp: algo-bit i2c-core |
|---|
| 84 | I2C bus through the parallel port, Philips interface |
|---|
| 85 | Do not insert this module unless you are sure you have this interface; |
|---|
| 86 | it will block your parallel port, and cause fake devices to appear. |
|---|
| 87 | Module parameters: |
|---|
| 88 | base (i) Base address of parallel port |
|---|
| 89 | |
|---|
| 90 | (i2c) bit-velle: algo-bit i2c-core |
|---|
| 91 | I2C bus through the parallel port, Vellemann K9000 interface |
|---|
| 92 | Do not insert this module unless you are sure you have this interface; |
|---|
| 93 | it will block your parallel port, and cause fake devices to appear. |
|---|
| 94 | Module parameters: |
|---|
| 95 | base (i) Base address of parallel port |
|---|
| 96 | |
|---|
| 97 | (i2c) i2c-dev: i2c-core |
|---|
| 98 | /dev interface for I2C adapters. This will be superseded by a module which |
|---|
| 99 | will also implement SMBus access. |
|---|
| 100 | |
|---|
| 101 | (i2c) hw-monitor: ??? |
|---|
| 102 | Old skeleton driver for GL518SM. Will be superseded by a module which |
|---|
| 103 | interfaces with the sensors module. |
|---|
| 104 | |
|---|
| 105 | Several other modules are not yet ported by Simon Vogl. They are mostly in |
|---|
| 106 | i2c/old-code. |
|---|