Many thanks to Hans, Mark and Jonathan for answering my previous email on specific hwmon chips (turns out 3 of the 4 I questioned are not (yet) supported by lm-sensors). I'd like to back-up a bit and ensure I understand what lm-sensors will do for us in our project: Essentially, we want to be able to read our temp and power monitor chips every 10 seconds and evaluate the values read (pass them for review to our own customized health monitoring system). I've been tasked with explaining the benefits of using lm-sensors package vs. not using it. Hopefully my questions do not seem too naive but I'm asking them from the perspective of having to write drivers (or, at least, assisting) for unsupported chips: - As I understand it, the drivers for these chips are not part of lm-sensors; one must develop the code for the chip in the kernel, if not already supported by the kernel. This driver work, if needed, is done whether or not one chooses to use lm-sensors, correct? - The libsensors library makes things easier by offering an interface for apps to access chip readings, configure them and convert them to real-world values. It works in conjunction with the /etc/sensors.conf file. o Is libsensors part of lm-sensors or are they developed and retrieved independently? o Is lm-sensors considered one of the "apps" mentioned above that opt to use libsensors to make things easier? o Can I choose to write my own app to interface with libsensors and the hwmon chips? One of my colleagues asked "why can't we simply read the chip registers with simple i2c calls over the bus?". - I skimmed over the lm-sensors source code. I know that it was made generic. So, how does it know what chips it needs to monitor? I assume this is through the sensors.conf file. I'm looking for the: o lm-sensors source code that discovers the chips that it has (does it read the sensors.conf file? Where is the lm-sensors code that does this?) o lm-sensors source code that utilizes the kernel drivers that sit in /drivers/hwmon directory. Could you point me to this code? If the info I am looking for is already in some doc'n somewhere, feel free to point me to it. I have perused a good bit of doc'n by now but maybe I've missed it. Thanks for your helpful comments and tips. Rob Bloom Software Design Engineer Flextronics Canada Design Services Legal Disclaimer: The information contained in this message may be privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete or destroy any copy of this message -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20090528/04f8ab97/attachment.html
