It compiles now cleanly against kernel 2.0.36; I checked, double-checked and
cross-checked.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@247 7894878c-1315-0410-8ee3-d5d059ff63e0
All our own code (ie. anything not in the i2c directory) compiles now without
warnings, even with WARN=1 (which sets -Wall -Wstrict-prototypes -Wshadow
-Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Wnested-externs
-Winline). There is one exception: the lex code (conf-lex.l) complains about
unused functions. That's flex' fault, not ours!
The i2c code still emits many warnings with the above flags; that's Simon's
problem.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@233 7894878c-1315-0410-8ee3-d5d059ff63e0
Renamed sensors entry from "SiS 5595 Sensor-*" to "sis5595-*"
Added this name in sensors.conf.eg to use lm78 names for inputs.
Small related document updates.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@199 7894878c-1315-0410-8ee3-d5d059ff63e0
integrated LM78, so the driver is only a customized copy of lm78.c
This southbridge can also do i2c, but this not enough documented in
the datasheet. So i2c is currently not supported.
Some cosmetic changes for VIA driver and documentation.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@196 7894878c-1315-0410-8ee3-d5d059ff63e0
It tries to delete bit-via.o, bit-mb.o, isa.o and piix4.o in the module
install directory.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@194 7894878c-1315-0410-8ee3-d5d059ff63e0
lm_sensors2 source tree. Improvements in VIA driver,
now checks revision code and refuses to load the
module if bit_test (in algo-bit) fails.
(Also fixes previous unsuccessfull CVS commit)
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@187 7894878c-1315-0410-8ee3-d5d059ff63e0
I really hope I did not forget an add or remove. If strange things happen
when you compile, please let me know.
There may still be problems with the EXPORT_* stuff; it seems to work now
for kernel 2.0.36pre19, but it may give trouble for earlier kernels. We
need to check that.
Some i2c modules may be a bit verbose at this moment.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@184 7894878c-1315-0410-8ee3-d5d059ff63e0
Until now, all installed include files depended on a #defined variable
LM_SENSORS: if it was defined, other files were included as "somefile.h"
instead of <linux/somefile.h>. This was clearly dangerous, and is fixed
now, by automatically deleting the offending lines from the include file
when it is installed.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@180 7894878c-1315-0410-8ee3-d5d059ff63e0
I added two new make file 'includes': busses/Module.mk and chips/Module.mk
Frodo- You may want to review the makefile structure to make sure that
the system works as you intended.
Note: The docs still need to be updated to reflect the new file arrangement,
but at least it builds!
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@176 7894878c-1315-0410-8ee3-d5d059ff63e0
output to ADM9240. Status/alarms values need to be implemented instead
of a raw output, but I'll do that too.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@173 7894878c-1315-0410-8ee3-d5d059ff63e0
Everything is in, except the IOCTL hook (which will be pretty simple to add).
It compiles cleanly. It is not tested at all.
Also a very small fix for i2c-proc, and Makefile.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@158 7894878c-1315-0410-8ee3-d5d059ff63e0
switch. It can switch two devices which each consume 300mA at 5V (or less).
This is good for fans, lights, or into relays for heftier stuff.
Here's what the usage looks like:
[root@penn sensors]# ls ltc1710-i2c-1-58/*
ltc1710-i2c-1-58/switch1
ltc1710-i2c-1-58/switch2
[root@penn sensors]# cat ltc1710-i2c-1-58/*
0
0
[root@penn sensors]# echo "1" > ltc1710-i2c-1-58/switch2
(blue LED turned on)
[root@penn sensors]# cat ltc1710-i2c-1-58/*
0
1
One problem with the device: It doesn't support reads. It ignores any
read transactions, so even detection with a read won't work. This
also means that the status of the switches has to be remembered and
can't be polled.
As simple as this device is, it is one of the few which actually
allows the computer to send signals OUT into the world to
control something.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@155 7894878c-1315-0410-8ee3-d5d059ff63e0
basically an expanded LM75. It can have an external temp probe (in
addition to the internal one), customizable conversion rate (in # of times
per second, depending on power consumption requirements), and
actually has a device-id register for easier/more-certain detecting!
The only strange property is the low-limit. The low-limit doesn't act
as a Hystersis value like the LM75. I.e., if the temp falls below it,
it triggers an alarm instead of clearing it. Strange, ey? This makes
using the chip for a thermostat control (like for a fan) much harder.
But it *could* be used to turn on a heater to prevent your computer from
freezing. :')
Here's what my output looks like (without a remote sensor. temp's
are the same format as the LM75 [high-limit, low-limit, value]):
[root@penn adm1021-i2c-0-18]# ls -l
total 0
-r--r--r-- 1 root root 0 Jan 9 23:42 die_code
-rw-r--r-- 1 root root 0 Jan 9 23:42 remote_temp
-r--r--r-- 1 root root 0 Jan 9 23:42 status
-rw-r--r-- 1 root root 0 Jan 9 23:42 temp
[root@penn adm1021-i2c-0-18]# cat *
3
60 20 0
76
60 20 24
PS- all temp values in the ADM1021 (limits and readings) are signed
(2's comp) bytes. So, all readings go from -128 to 127 C (actually,
the docs say it can only reliable sense down to -65), and only
in whole degree increments.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@153 7894878c-1315-0410-8ee3-d5d059ff63e0
* Better VDD internal computation, as described in the data sheet;
* Fixed the config file to reflect the above change;
* The library read the wrong file to get its gl518sm alarm data.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@150 7894878c-1315-0410-8ee3-d5d059ff63e0
When computing the fan rotation speed, the register value of the dividers
was used, instead of the value it represents. I'ev fixed this ages ago
for the LM80 driver, but it seems I had forgotten to fix it at other places.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@149 7894878c-1315-0410-8ee3-d5d059ff63e0
Read the intro; it describes how you can use CVS to diff between old releases.
Stupid copyright typo in piix4.c fixed
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@146 7894878c-1315-0410-8ee3-d5d059ff63e0
* (module) VIN limits are now set to sane values (3V instead of 30V, which
caused nasty overflows)
* (module) VIN limits had min/max swapped in gl518_attach_adapter
* (lib) TEMP_HYST used the VID sysctl instead of the TEMP sysctl, leading
to bogus readings
* (sensors) print n/a for gl518 not available readings.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@145 7894878c-1315-0410-8ee3-d5d059ff63e0
readings. (changed a u8 to a u16 in the data struct.) Now the temp
readings seem to work perfectly!
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@136 7894878c-1315-0410-8ee3-d5d059ff63e0
This could lead to memory corruption and to the could-not-unload-module
problem of earlier reports. With a little luck, this will resolve all
module loading/unloading problems reported.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@132 7894878c-1315-0410-8ee3-d5d059ff63e0
Philip Edelbrock