as the BIOS is supposed to set them up properly. This information makes it
easier to find out which temperature channel corresponds to the CPU.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@4456 7894878c-1315-0410-8ee3-d5d059ff63e0
based on preliminary work by Yuan My (Winbond). Thanks to Bernardo Motta
at Observit for providing the hardware that made it possible.
Note that support for the W83627DHG isn't included, but it could easily be
added later is anyone needs it.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@4447 7894878c-1315-0410-8ee3-d5d059ff63e0
* Check for configuration file validity
fancontrol and pwmconfig:
* Support optional min and max PWM values
Documentation updated accordingly.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@4438 7894878c-1315-0410-8ee3-d5d059ff63e0
* No longer depend on grep. We already depend on egrep so let's use it
everywhere.
* Don't depend on awk to compute the target PWM value. Bash has an arithmetic
expression evaluation engine which does the job just fine.
* Use read instead of cat to read the sensor values. read is built-in, so
it's cheaper.
* When sysfs is used (2.6 kernel), do not postproces the sensor value reads
with cut, as it is not needed.
* Update the dependency list.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@4437 7894878c-1315-0410-8ee3-d5d059ff63e0
* Use let for arithmetic evaluation. Patch taken from the Suse package.
* Kill old commented-out code.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@4436 7894878c-1315-0410-8ee3-d5d059ff63e0
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/trunk@4404 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
of in /usr/local/sbin. Many users have been complaining and several
distribtions were (rightly) modifying sensors-detect because of this.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@4358 7894878c-1315-0410-8ee3-d5d059ff63e0
sequence to the longer one, and stop as soon as one enter sequence worked.
This avoids false positives.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@4353 7894878c-1315-0410-8ee3-d5d059ff63e0
If we find that the register at offset 5 doesn't behave as it would for
an LM78 or W83781D chip, attempt to restore its 8 original bits rather
than just the 7 LSB.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@4347 7894878c-1315-0410-8ee3-d5d059ff63e0
a RTC chip. We detect it only because it lives at address 0x50, which is
also used by some hardware monitoring chips and most notoriously EEPROMs.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@4343 7894878c-1315-0410-8ee3-d5d059ff63e0
removal. In recent kernels we can detect i2c-isa devices by checking
the i2c bus number: i2c-isa always uses 9191 as its bus number.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@4337 7894878c-1315-0410-8ee3-d5d059ff63e0
physical device. This change is required to survive the planned struct
class_dev removal from future 2.6 kernels.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@4326 7894878c-1315-0410-8ee3-d5d059ff63e0
The i2c-ali1563 initialization looks quite broken to me:
* If the I/O space isn't enabled, we forcibly set 3 bits in
the PCI configuration space instead of just the one enabling
the I/O space.
* After that we pretend to check if the write worked, but we
don't actually read the new value from the register.
* It's probably not a good idea to enable the I/O space if no
base address has been set.
So I propose the following changes to that part of the driver:
* Merge ali1563_enable() into ali1563_setup().
* Check the base address before the I/O space enabled bit.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@4324 7894878c-1315-0410-8ee3-d5d059ff63e0
* Add an explicit mask when writing the low byte of a word.
* Use I2C_SMBUS_BLOCK_MAX instead of hardcoding 32.
* Use boolean not instead of bitwise not for bit tests, it's clearer.
* Return proper error values rather than -1.
* Fix a race on device registration, initialization should be done
before the bus is registered.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@4318 7894878c-1315-0410-8ee3-d5d059ff63e0
easier to find out which specific address causes problem if the system
freezes or the SMBus locks itself, for example.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@4316 7894878c-1315-0410-8ee3-d5d059ff63e0
focus of the script, so their handling shouldn't take more time and
code than strictly necessary.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@4313 7894878c-1315-0410-8ee3-d5d059ff63e0
was using a brute force approach, quite reliable but very slow. The new
code should be just as reliable but about ten times faster.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@4312 7894878c-1315-0410-8ee3-d5d059ff63e0
easier to see what is being tried in real time, in particular if the
probing locks for any reason.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@4311 7894878c-1315-0410-8ee3-d5d059ff63e0
- Only probe I2C addresses for which we know at least one device. This will
speed up the probing a bit, and hopefully limit both user and hardware
confusion.
- Drop ARP-capable device detection, we don't do anything useful with
the information and we have no other reason to probe I2C address 0x61.
i2cdetect can be used instead when we want to know more about a given
I2C bus.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@4304 7894878c-1315-0410-8ee3-d5d059ff63e0
* Disable debugging by default
* Add support for non-i2c drivers
* More tolerant config file parsing (for some reason pwmconfig
adds unneeded spaces, it should probably be fixed but it's always
better to be tolrant nevertheless)
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@4295 7894878c-1315-0410-8ee3-d5d059ff63e0
Jean Delvare