Christian Emmerich wrote: > Hi Riku, > > > Thanks for your time reviewing and testing the driver. > No problem. Without the driver i would't be able to manage the > temperature/fan speed of my pc, so i have to thank you for your work. > > > > temp1_max_hyst > > ALL6500:/sys/devices/platform/IOP3xx-I2C.0/i2c-0/0-002e# cat > temp1_max_hyst > > 61000 > > > So it appears to work as expected. According to sysfs-interface temp* > > should report and accept millidegrees or millivolts. We are outputting > > millidegrees. > > OK, this was my fault if i set the value by hand i could also see the > value using 'cat temp1_max_hyst' and sensors, i thought there would be > an automatic entry i can read out. > What does this value exactly stand for, is it usefull for sensors or > just a value i can read out using sensors? > It has a default value, 60 degrees, but your bios might overwrite it. Which reminds me: if you don't mind, please verify that values reported by sensors match the ones reported by bios. Often bios's come with a screen that shows of hwmon information. as I understand, hysteresis is a kind of "soft" limit, or warning zone before the critical temperature hits. > Another problem i forget in my last mail. I don't know what's the > reason, but if i do the following: > root at pc:/sys/devices/pci0000:00/0000:00:01.1/i2c-1/1-002d# cat fan1_min > i got following output: > <output> > root at pc:/sys/devices/pci0000:00/0000:00:01.1/i2c-1/1-002d# cat fan1_min > Segmentation fault > root at pc:/sys/devices/pci0000:00/0000:00:01.1/i2c-1/1-002d# Oops. the new REG_TO_RPM code did not take in account if the rpm count is zero.. should be fixed with the attached version.. -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Add-f75375s-driver.patch Type: text/x-patch Size: 23517 bytes Desc: not available Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20070710/35e5374e/attachment.bin
