mirror of
https://github.com/lm-sensors/lm-sensors.git
synced 2026-11-06 15:51:34 +00:00
Other main files updated.
Can people please update the CHANGES file? The current text is a cop-out :-) git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@568 7894878c-1315-0410-8ee3-d5d059ff63e0
This commit is contained in:
1 parent
b7bb64350c
commit
8f771dc758
4 files changed
+10
-3
No files matched your search
+2
-1
@@ -6,7 +6,8 @@ understand what you are seeing happen.
|
||||
When you want to communicate with a piece of hardware, you need a kernel
|
||||
driver (well, that is not quite true, but it is in most cases the only
|
||||
way to do it safely). In the past, this meant you had to patch the kernel
|
||||
and recompile it. These days, you can use kernel modules.
|
||||
and recompile it. These days, you can use kernel modules. We support both
|
||||
approaches.
|
||||
|
||||
We have chooses for a very modular (no pun intended) setup. There are a
|
||||
few general-purpose base kernel modules, which you always need. In
|
||||
|
||||
@@ -59,4 +59,4 @@ Kernel i2c conflict
|
||||
|
||||
An older version of the i2c modules is distributed in 2.2 and late 2.1
|
||||
kernels. If you try to use it at the same moment as our i2c modules, you
|
||||
may get into trouble. There is no nice solution for this yet.
|
||||
may get into trouble. This should be fixed for lm_sensors-2.4.0 and newer.
|
||||
@@ -13,6 +13,11 @@ ask CVS about it:
|
||||
for example:
|
||||
cvs diff -r V2-0-0 -r V2-0-1 -u
|
||||
|
||||
2.4.0 (19990920)
|
||||
Too much to list.
|
||||
i2c and smbus parts are split off to a separate i2c package.
|
||||
New drivers and other stuff.
|
||||
|
||||
2.3.4 (19990616)
|
||||
Module matorb: driver for Matrix-Orbital Displays (small LCD and VFDs)
|
||||
All: Now compiles against kernel 2.0.x (again ;)
|
||||
|
||||
@@ -9,7 +9,8 @@ has its own strong points. They are:
|
||||
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.
|
||||
YOU WILL STILL HAVE TO COMPILE THIS PACKAGE TO GET THE USERLAND UTILITIES!
|
||||
AFTER YOU COMPILED AND INSTALLED YOUR KERNEL, YOU WILL STILL HAVE TO
|
||||
COMPILE THIS PACKAGE TO GET THE USERLAND UTILITIES!
|
||||
|
||||
Each of these ways will be described below in detail.
|
||||
|
||||
|
||||
Reference in new issue
Block a user