|Version 6 (modified by khali, 7 years ago)|
Downloading i2c and lm_sensors
This software is OSI Certified open source software. OSI Certified is a certification mark of the Open Source Initiative.
i2c and lm_sensors v2.10.0
This is the latest release of the current project, for Linux 2.4.10+. This is a stable release with support for most devices. Userspace tools support 2.4 and 2.6 kernels. Modules will not compile on 2.6 kernels (use those coming with the kernel itself). Note that LM Sensors 2.10.0 requires I2C 2.9.0 or newer. See the I2C changes document for details of changes in I2C 2.10.0.
- You will need to install the libsysfs library (or a dev package from your distribution) if you want support for Linux 2.6, because libsensors now depends on it.
- This release supersedes, and is not compatible with, 2.8.x releases. The 2.8.x series is considered deprecated and unsupported. Third party i2c driver authors are invited to drop support for this broken series.
i2c-2.10.0 (135 kB)
See below for an i2c-2.10.0 Linux kernel patch.
Linux 2.6 users do not need to get this i2c package, it's already part of the kernel tree.
lm_sensors-2.10.0 (860 kB)
lm_sensors-2.10.0.tar.gz (HTTP mirror)
i2c and lm_sensors v2.7.0
This is the last 2.2/2.3 kernel-compatible release (including 2.4 kernels through 2.4.9). Note that LM Sensors 2.7.0 requires I2C 2.7.0.
lm_sensors-2.7.0.tar.gz (HTTP mirror)
This is the last 2.0 kernel-compatible release.
lm_sensors-2.4.5.tar.gz (HTTP mirror)
This is the latest stable release of the original project. This release is in a "tested and deemed stable" status. This is a simple version which is well tested and supports some common hardware health monitoring chips. This may not work on newer hardware or kernels. We no longer support this code.
lm_sensors-1.4.12.tar.gz (HTTP mirror)
- Users who have a monolithic (as opposed to modular) kernel or simply want some i2c drivers built-in will need to patch their kernel tree. A minor incompatibility issue exists with two drivers (bttv and tvmixer) in the Linux 2.4.23 to 2.4.28 kernels. A complete installation guide with patches is available here.
- 2.4 and 2.5 kernel patches were made available by Albert Cranford here (out of date).
- Steven J. Hill also has patches for the 2.4.21 and 2.4.22 kernels here (untested).
- RPMs for Red Hat 7.3, 8.0 and 9, and Fedora Core 1, were made available by Axel Thimm on his ATrpms website. You need to use the i2c/lm_sensors-enabled kernels from the same site.
- You can access all released files here.
Anonymous access to our Subversion repository (SVN) is available. This means that users can have direct access to up-to-the-minute code.
Driver development for 2.6 kernels is taking place directly in the kernel using GIT. Do not use the drivers from our SVN repository for 2.6 kernels, it will not work. The user-space tools will work though.
We presume that you have Subversion installed on your machine. To check out a working copy of the code for this project use the following commands:
svn checkout http://lm-sensors.org/svn/i2c/trunk i2c svn checkout http://lm-sensors.org/svn/lm-sensors/trunk lm-sensors
To update the code, do a svn update from within the i2c or lm-sensors directories. Please read the README and INSTALL files of your working copy for how to build the code. Also read the related files in the 'doc' directory for info regarding the different bus and chip drivers. Lastly, you can use the regular svn commands on the files (like cvs log [filename]) to see the comments made by the developers as changes were made.
If you're not familiar with the use of Subversion we recommend the excellent Subversion book which is a valuable resource.
Commits to the repositories are notified on the lm-sensors-notify mailing-list. Feel free to subscribe if you want to be informed of the changes made to the i2c and lm-sensors repositories.
Browse the Distribution
Choose the links below to view the current development code:
- i2c (source code and documentation)
- lm-sensors (source code and documentation)
Nightly CVS snapshots
Note: We're currently switching away from CVS to Subversion. Up to now there are no snapshots available from the subversion repository. Hence the CVS snapshots are still provided as a work-around. However, the CVS repository is not updated any longer, so please be aware that you won't see all of the changes that eventually are available in the Subversion repository.