be available in Linux kernel 2.6.23. Binary compatibility is guaranteed,
source code compatibility isn't, but the incompatibility will be
spotted quickly as the prototype of the helper function
i2c_smbus_read_i2c_block_data() changed. The only problem would be if
a program is calling i2c_smbus_access() directly. Hopefully this should
be a rare case. The py-smbus binding code is in this case and will be
adjusted soon.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@4417 7894878c-1315-0410-8ee3-d5d059ff63e0
back from the address port, so the value 0xff is returned, causing
a false positive with the original test. Testing explicitly for 0x80
instead of only testing that bit 7 is set, works around it.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/branches/lm-sensors-3.0.0@4406 7894878c-1315-0410-8ee3-d5d059ff63e0
back from the address port, so the value 0xff is returned, causing
a false positive with the original test. Testing explicitly for 0x80
instead of only testing that bit 7 is set, works around it.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@4404 7894878c-1315-0410-8ee3-d5d059ff63e0
moving to a user-space-only package, all the drivers are maintained in
the Linux kernel tree itself.
I tried to update the documentation a bit, but there's still a lot to
go. In fact, a complete rewrite seems to be needed.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/branches/lm-sensors-3.0.0@4397 7894878c-1315-0410-8ee3-d5d059ff63e0
from the openSuse sensors package. This is a good idea because the
PWM/speed relation isn't linear, and it is frequent that the speed
changes are concentrated in the low PWM range.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/branches/lm-sensors-3.0.0@4381 7894878c-1315-0410-8ee3-d5d059ff63e0
from the openSuse sensors package. This is a good idea because the
PWM/speed relation isn't linear, and it is frequent that the speed
changes are concentrated in the low PWM range.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@4380 7894878c-1315-0410-8ee3-d5d059ff63e0
* Delete sample lm_sensors.sysconfig file, it is now generated by
sensors-detect.
* Fix several occurences of the configuration file name.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@4378 7894878c-1315-0410-8ee3-d5d059ff63e0
* Update Makefile and README to mention hwmon class for newer
2.6 kernels
* Add missing shell declarations
* Update URI
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@4373 7894878c-1315-0410-8ee3-d5d059ff63e0
* Drop outdated reference to /proc/sys/dev/sensors
* Bus type can be pci
* Make the examples more realistic
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@4370 7894878c-1315-0410-8ee3-d5d059ff63e0
monitoring devices are better accessed through the hwmon class. Original
patch from Jeff Kosowsky.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@4369 7894878c-1315-0410-8ee3-d5d059ff63e0
identify sysfs entries. Reasons for this rewrite / bugs fixed:
-Don't give features like alarms / sensor type / fault flag a
compute mapping only a normal mapping
-Don't generate features for sysfs entries like uvent, modalias, etc.
instead only generate features for features known by
sensors_feature_get_type()
-Sort the list of found features logically instead of sorted in alphabet order
of the sysfs entry. So now it starts with all in entries, then all fan and
then all temp. Just like the order of most entries in lib/chips.c. Also
this means that it now contains in0 - in10 in that order and not in0, in10,
in1 - in9
git-svn-id: http://lm-sensors.org/svn/lm-sensors/branches/lm-sensors-3.0.0@4368 7894878c-1315-0410-8ee3-d5d059ff63e0
abituguru seems to work well with the new dynamic chip support and generic
chip printroutines. note: the abituguru code should be completly removed in
the future.
-comment k8temp entry in lib/chips.c and prog/sensors/main.c, as the
k8temp seems to work well with the new dynamic chip support and generic
chip printroutines. note: the k8temp code should be completly removed in
the future.
-make the match for the subtype exact instead of a strncmp, otherwise
an alarm_enable flag gets classified as an alarm, leading to all sensors who
have their alarm enabled getting an alarm reported, as the alarm_enabled gets
read as alarm.
-and do the same for the _input match to check if this is a main or subfeature
git-svn-id: http://lm-sensors.org/svn/lm-sensors/branches/lm-sensors-3.0.0@4367 7894878c-1315-0410-8ee3-d5d059ff63e0
Jean Delvare