Show
Ignore:
Timestamp:
09/24/06 18:36:34 (7 years ago)
Author:
khali
Message:

Documentation update. I tried to remove or update all outdated stuff, it
looks better now, but that's still quite a mess which we'd need to cleanup.

Files:
1 modified

Legend:

Unmodified
Added
Removed

  • lm-sensors/trunk/BACKGROUND

    r568 r4173  
    1616 
    1717The kernel modules communicate their information through both the /proc 
    18 and sysctl interfaces. To keep things uncomplicated, the sensor chips always  
    19 advert their measurements 'as is'. This means that the values they 
    20 report are not immediately relevant to you - they must first be scaled 
    21 and translated to correspond to the real world. 
     18and sysctl interfaces (Linux 2.4) or the /sys interface (Linux 2.6). To 
     19keep things uncomplicated, the sensor chips always advert their 
     20measurements 'as is'. This means that the values they report are not 
     21immediately relevant to you - they must first be scaled and translated 
     22to correspond to the real world. 
    2223 
    2324It is also possible to communicate directly with chips on an I2C bus 
    2425or SMBus. This is done through /dev files. This is useful if you  
    2526quickly want to test how a certain chip behaves, without having to 
    26 write a kernel driver. It is also dangerous; several applications could 
    27 access the same chip at the same time. 
     27write a kernel driver. 
    2828 
    2929Note that all other parts of this package function in so-called user-space. 
    … …  
    3232 
    3333Applications could (and can) directly read the sensor values through the  
    34 /proc or the sysctl interfaces. This is harder then it sounds; because 
     34/proc, sysctl or /sys interfaces. This is harder than it sounds; because 
    3535no two chips are the same, the information they communicate may also 
    3636be very unlike. This would mean that every application would have to know 
    … …  
    5757 
    5858This package does not contain a nice graphical monitor. Look at the file 
    59 doc/useful_addresses for pointers to such programs. It does contain an 
    60 example console program that reports all current sensors values. This 
     59doc/useful_addresses.html for pointers to such programs. It does contain 
     60an example console program that reports all current sensors values. This 
    6161program is called 'sensors'. You can use it as a reference implementation 
    6262for more intricate programs.