- 09/24/06 18:36:34 (7 years ago)
- 1 modified
r568 r4173 16 16 17 17 The 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. 18 and sysctl interfaces (Linux 2.4) or the /sys interface (Linux 2.6). To 19 keep things uncomplicated, the sensor chips always advert their 20 measurements 'as is'. This means that the values they report are not 21 immediately relevant to you - they must first be scaled and translated 22 to correspond to the real world. 22 23 23 24 It is also possible to communicate directly with chips on an I2C bus 24 25 or SMBus. This is done through /dev files. This is useful if you 25 26 quickly 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. 27 write a kernel driver. 28 28 29 29 Note that all other parts of this package function in so-called user-space. … … 32 32 33 33 Applications could (and can) directly read the sensor values through the 34 /proc or the sysctl interfaces. This is harder then it sounds; because 34 /procn it sounds; because 35 35 no two chips are the same, the information they communicate may also 36 36 be very unlike. This would mean that every application would have to know … … 57 57 58 58 This 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 59 doc/useful_addressesn 60 example console program that reports all current sensors values. This 61 61 program is called 'sensors'. You can use it as a reference implementation 62 62 for more intricate programs.