All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] lm-sensors 3.0.0-rc1 has been released!
Date: Tue, 25 Sep 2007 21:33:16 +0000	[thread overview]
Message-ID: <20070925233316.7afaa297@hyperion.delvare> (raw)

Hi all,

As announced last week, I released a first release candidate (rc1) of
lm-sensors 3.0.0. The API is supposedly OK now, so it's time for
application authors to try and port their applications to the new
library and send us feedback.

Important changes compared to lm-sensors 2.10:
* lm-sensors 3 only supports kernels 2.6.5 and later.
* It is now a user-space-only package, it no longer contains kernel
  drivers.
* The i2c tools have been moved to a separate package (surprisingly
  named i2c-tools).
* libsensors version was bumped to 4.0.0, as it has a completely new
  API we had to increase the .so version. This new library contains
  no chip-specific knowledge, it assumes that hardware monitoring
  drivers follow the standard sysfs interface.
* The "sensors" binary has temporarily been renamed to "sensors3", so
  that you can keep the old version around for comparison purpose. It
  will be renamed back to "sensors" just before lm-sensors 3.0.0 is
  released.
* sensors.conf is not fully compatible between the old and the new
  library. The lm-sensors 3 package includes a conversion script
  from the old format to the new one.

There's one remaining open task for lm-sensors 3.0.0:
http://www.lm-sensors.org/ticket/2174
Mark, this is yours. If you don't think you'll have the time to
implement it quickly, please move it to milestone 3.0.1.

lm_sensors-3.0.0-rc1.tar.gz is not signed yet. Phil, do you want to
keep signing the archives for the lm-sensors 3 series? If you want to
do it, please proceed. If you prefer that I take over, just say so and
I'll do it.

Notes to application authors:
* The new library has no chip-specific knowledge. As a result, the
  <sensors/chips.h> header file is gone.
* Pretty much all functions of the old API are gone or work
  differently. If you need to test for the new library in some
  configure script, sensors_get_features, sensors_get_all_subfeatures
  and sensors_get_subfeature are good candidates. Alternatively, you
  can test that the libsensors_version string starts with "3." or
  explicitly ask for libsensors.so.4.
* Reloading the configuration file with sensors_init() is no longer
  supported, you need to explicitly call sensors_cleanup() before you
  can call sensors_init() again.
* There's no porting guide available. The new API is so different from
  the old one that you're probably better looking at an application
  using the new API to get an idea how it works. It's not very
  difficult. The "sensors" and "sensord" applications that are part of
  the lm-sensors package have been ported to the new API already, so
  they are good examples. "sensors" in particular is very simple.

I've ported xsensors already, the patch is available here:
http://jdelvare.pck.nerim.net/sensors/xsensors-libsensors4.patch

I'll do the Freshmeat announcement tomorrow.

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

             reply	other threads:[~2007-09-25 21:33 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-25 21:33 Jean Delvare [this message]
2007-09-25 21:45 ` [lm-sensors] lm-sensors 3.0.0-rc1 has been released! Philip Edelbrock
2007-09-26 21:02 ` Hans de Goede
2007-09-27 14:35 ` Jean Delvare
2007-09-27 14:42 ` Jean Delvare
2007-09-27 17:53 ` Henrique de Moraes Holschuh
2007-09-28 17:07 ` Jean Delvare
2007-09-28 20:13 ` Henrique de Moraes Holschuh
2007-09-29 13:39 ` Jean Delvare
2007-09-30  0:56 ` Henrique de Moraes Holschuh
2007-09-30 11:54 ` Jean Delvare
2007-09-30 12:10 ` Jean Delvare
2007-09-30 14:54 ` Henrique de Moraes Holschuh
2007-10-03 10:36 ` Jean Delvare
2007-10-03 11:38 ` Henrique de Moraes Holschuh
2007-10-04  9:45 ` Jean Delvare
2007-10-04 12:49 ` Henrique de Moraes Holschuh
2007-10-04 13:42 ` Jean Delvare
2007-10-07 11:21 ` Axel Thimm
2007-10-17 21:44 ` Jean Delvare
2007-10-18  7:17 ` Hans de Goede
2007-10-18  8:18 ` Aurelien Jarno
2007-10-19 14:46 ` Jean Delvare
2007-10-19 20:18 ` Hans de Goede
2007-10-20 18:13 ` Jean Delvare
2007-10-20 22:41 ` Hans de Goede
2007-10-21 19:08 ` Jean Delvare
2007-10-21 19:13 ` Hans de Goede
2007-10-21 21:12 ` Jean Delvare
2007-10-22  7:06 ` Hans de Goede
2007-10-22  7:48 ` Jean Delvare
2007-10-22  8:13 ` Hans de Goede
2007-10-22  8:23 ` Jean Delvare
2007-10-22  9:40 ` Hans de Goede
2007-10-22 11:55 ` Jean Delvare
2007-10-22 13:15 ` Hans de Goede
2007-10-22 13:55 ` Jean Delvare
2007-10-22 19:27 ` Hans de Goede
2007-10-22 22:25 ` Aurelien Jarno
2007-10-24 15:30 ` Jean Delvare
2007-10-24 17:09 ` Hans de Goede

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070925233316.7afaa297@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=lm-sensors@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.