From: Jean Delvare <jdelvare@suse.de>
To: Linux I2C <linux-i2c@vger.kernel.org>
Cc: "Angelo Compagnucci" <angelo.compagnucci@gmail.com>,
rpjday@crashcourse.ca, "Ondřej Lysoněk" <olysonek@redhat.com>
Subject: i2c-tools 4.0 has been released
Date: Mon, 30 Oct 2017 11:10:50 +0100 [thread overview]
Message-ID: <20171030111050.31f82e26@endymion> (raw)
Hi all,
After 6 years of waiting, a new version of i2c-tools is finally out. It
marks a significant milestone of the project, because we finally got
rid of the huge ugly i2c-dev.h header file full of inline functions
that was interfacing with the kernel, and replaced it with a small
library. This means no more code duplication, no more compiler
warnings, and no more confusion and collision with kernel header files.
Hopefully.
Note that libi2c is released under the LGPL, as you would expect for a
library.
You can download i2c-tools 4.0 at the usual place:
https://www.kernel.org/pub/software/utils/i2c-tools/
You can check the CHANGES file for a list of other improvements. Most
notably:
* Many fixes and improvements to decode-dimms, although unfortunately
it is still missing DDR4 support.
* New manual pages and examples added to existing manual pages.
* New tool written by Wolfram Sang to transfer raw I2C messages:
i2ctransfer.
* Support for python 3.
Please let me know if anything doesn't work or doesn't look good.
Thanks,
--
Jean Delvare
SUSE L3 Support
next reply other threads:[~2017-10-30 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 10:10 Jean Delvare [this message]
2017-10-30 13:23 ` i2c-tools 4.0 has been released Wolfram Sang
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=20171030111050.31f82e26@endymion \
--to=jdelvare@suse.de \
--cc=angelo.compagnucci@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=olysonek@redhat.com \
--cc=rpjday@crashcourse.ca \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox