Changeset 100

Show
Ignore:
Timestamp:
12/21/98 23:41:59 (10 years ago)
Author:
frodo
Message:

Documentation updates, small application update (still not doing
anything useful)

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved

  • lm-sensors/trunk/INSTALL

    r89 r100  
     1Please read this file thoroughly before you try to install and run things. It 
     2will safe you many headaches. Installation is not really difficult, but there 
     3are a few pitfalls. 
     4 
     5COMPILATION AND INSTALLATION 
     6============================ 
     7 
    18Basic installation is uncomplicated. Run 'make all', followed by an optional 
    29'make install'. Everything is compiled using the Makefile in the root of 
    …… 
    3946actually use these modules, you have a problem; they can not coexist 
    4047with Simon's modules. Theoretically, you should be able to replace 
    41 the old modules with the new stuff in our i2c directory, recompile 
    42 the kernel, and then compile our modules with I2C=0. If you try 
     48the old modules in the kernel tree with the new stuff in our i2c directory, 
     49recompile the kernel, and then compile our modules with I2C=0. If you try 
    4350this, please share the results with us! 
    4451 
    …… 
    4956be unable to insert the modules at all, or you can expect strange  
    5057behaviour (probably leading to crashes). 
     58 
     59 
     60TESTING AND RUNNING 
     61=================== 
    5162 
    5263When you have compiled this package, you will be left with a lot of modules. 
    …… 
    6576 
    6677If you have installed the modules, as described within doc/modules, you can 
    67 do 'modprobe piix4 && modprobe lm78 && modprobe i2c-proc' (the last is 
    68 optional) from any directory to reach the same situation. 
     78do 'modprobe isa && modprobe piix4 && modprobe lm78 && modprobe i2c-proc'  
     79(the last is optional) from any directory to reach the same situation. 
     80 
     81This package also contains a library of functions which can be used to 
     82access sensor data in a more programmer-friendly way. It will be built as 
     83both a shared and a static library, and installed in your LIB directory 
     84(normally /usr/local/lib). It needs a configuration file, which is usually 
     85called 'sensors.conf', and can be placed in /etc, /usr/lib/sensors, 
     86/usr/local/lib/sensors, /usr/lib, or /usr/local/lib. [NOTE: No real 
     87standard config file is written yet. A very simple example can be found in  
     88the prog/sensors directory.] 
    6989 
    7090Where version 1 of this package had the human-readable /proc/sensors file, 
    71 this version will include a user-space program which gathers all data 
    72 and displays it in a comparable format. Regrettably, this program is not 
    73 yet finished. To understand the files that are present now, read doc/lm78,  
    74 doc/lm75 etc. 
     91this version includes a user-space program which gathers all data 
     92and displays it in a comparable format. This program is called 'sensors'. 
     93Everybody can use it to read sensors values; only root can use it to 
     94set minimum and maximum values [NOTE: not yet implemented] 
     95 
     96If you want to run 'sensors' without installing the package, you must 
     97use the following command to make it able to find its shared library: 
     98  (bash) export LD_LIBRARY_PATH=/WHEREVER/lm_sensors-2.X.Y/lib:$LD_LIBRARY_PATH 
     99  (tcsh) setenv LD_LIBRARYPATH /WHEREVER/lm_sensors-2.X.Y/lib:$LD_LIBRARY_PATH 
     100Replace /WHEREVER/lm_sensors-2.X.Y with the base directory of the package 
     101source code. 
    75102 
    76103One of the next releases of this package will have a user-space probe program, 
    77104which tells you which chips and busses are present, and which modules you 
    78105will have to load. At this moment, just try to load the modules; if no chip 
    79 or bus is detected, the module will fail to insert. 
     106or bus is detected, the module will fail to insert. [NOTE: not true for 
     107the bit-lp.o and bit-elv.o drivers. Don't try them without expecting  
     108fake devices] 
    80109 
    81 Please examine the files in the doc subdirectory for more information, or 
    82 try to mail us at <lm78@stimpy.netroedge.com>. Good luck! 
     110Please examine the files in the doc subdirectory for more information,  
     111especially about individual driver. You can always mail us at  
     112<lm78@stimpy.netroedge.com>. Alternatively, consider useing the (free) 
     113support site at http://www.netroedge.com/~lm78/support.html. Good luck! 

  • lm-sensors/trunk/README

    r57 r100  
    33a few changes compared with 1.x.y versions; read doc/version-2 for the 
    44most interesting ones. 
    5  
    65 
    76WARNING! This is a BETA release. It is not compatible with any programs 
    …… 
    1312good and bad, regarding this package with us at <lm78@stimpy.netroedge.com>. 
    1413 
     14WARNING! If you downloaded this package through our CVS archive, you walk 
     15the cutting edge. Things may not even compile! On the other hand, you will 
     16be the first to profit from new drivers and other changes. Have fun! 
     17 
    1518As a rule of thumb: if you have a PIIX4 with LM78/79 and LM75 chips, things 
    1619should run without problem. The GL518 driver is completely untested. All 
    1720supporting modules in the src directory should work without problem. If 
    1821you have a VIA chipset, we would like to hear whether you can access the 
    19 SMBus with it - this is not very well tested either. If you have a Winbond 
    20 chip, use the LM78/LM75 drivers until a specific Winbond driver is written. 
     22SMBus with it - this is not very well tested either. The new Winbond driver 
     23should basically work, though not all functionality may be present yet. 
    2124If you have a LM80, you are out of luck at this moment. 
    2225 

  • lm-sensors/trunk/prog/sensors/main.c

    r99 r100  
    118118int main (int argc, char *argv[]) 
    119119{ 
    120   int c; 
     120  int c,res; 
    121121 
    122122  struct option long_opts[] =  { 
    …… 
    149149  } 
    150150  open_config_file(); 
    151   exit(0); 
    152 } 
    153151 
    154  
    155  
    156 /* 
    157   if ((res = sensors_init(stdin))) { 
     152  if ((res = sensors_init(config_file))) { 
    158153    if (res == SENSORS_ERR_PROC) 
    159154      fprintf(stderr, 
    …… 
    164159    exit(1); 
    165160  } 
    166   for (i = 0; i < sensors_proc_bus_count; i++) 
    167     printf("%d: %s %s\n",sensors_proc_bus[i].number, 
    168            sensors_proc_bus[i].adapter,sensors_proc_bus[i].algorithm); 
    169161} 
    170  
    171 */