| | 57 | |
|---|
| | 58 | |
|---|
| | 59 | Mixing old and new, and using beta drivers (compilation option 1) |
|---|
| | 60 | ================================================================= |
|---|
| | 61 | |
|---|
| | 62 | It is possible that you are running a previously patched kernel, or |
|---|
| | 63 | a very new kernel which already has limited or full i2c or lm_sensors |
|---|
| | 64 | support, but you want to use newer versions of the drivers. This is |
|---|
| | 65 | possible, but there are some pitfalls. |
|---|
| | 66 | |
|---|
| | 67 | If had compiled all i2c and lm_sensors drivers as modules, you are |
|---|
| | 68 | in luck. You can simply compile the newest versions of i2c and |
|---|
| | 69 | lm_sensors and install them. Just make sure the right modules are |
|---|
| | 70 | loaded (best bet: remove the old ones first). |
|---|
| | 71 | |
|---|
| | 72 | If you have a certain driver compiled into your kernel, you may |
|---|
| | 73 | encounter bad problems. We do not guarantee to keep internal kernel |
|---|
| | 74 | interfaces unchanged. In plain language, this means that an older driver |
|---|
| | 75 | may not work together with a newer driver, and your kernel may crash. |
|---|
| | 76 | On the other hand, if you know what you are doing, compilation will |
|---|
| | 77 | be smart. Drivers that are compiled right into your kernel will not |
|---|
| | 78 | be compiled as a module again. You could do nothing with them anyway. |
|---|
| | 79 | |
|---|
| | 80 | Sometimes, you want to patch your kernel, but find that certain alpha |
|---|
| | 81 | or beta drivers are not included in the patch. This is on purpose: we |
|---|
| | 82 | do not want to polute the kernel tree with things of which we are not |
|---|
| | 83 | confident they work. In this case, patch the kernel, compile it, and |
|---|
| | 84 | then compile lm_sensors with COMPILE_KERNEL set to 1. |
|---|
