public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Linux I2C <i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org>
Subject: i2c-tools testers wanted
Date: Tue, 25 Mar 2008 12:04:21 +0100	[thread overview]
Message-ID: <20080325120421.71bb8977@hyperion.delvare> (raw)

Hi all,

I plan to release i2c-tools 3.0.1 soon (say beginning of April). The
most important changes since version 3.0.0 are:

* A new helper script for use with the i2c-stub kernel driver is
  included. It is named i2c-stub-from-dump and is installed by default.
  It can be used to feed i2c-stub from a chip register dump previously
  obtained using i2cdump. This can be very useful when working on a
  driver for an I2C/SMBus device you don't own.

* A new option to i2cdump, to let the user specify the register range
  to dump.

* Improvements to decode-dimms, contributed by Trent Piepho. The
  decoding of DDR2 SDRAM timings is complete now, and SPD data can be
  read from hexdumps.

* Minor improvements to decode-vaio, in particular support for recent
  kernels which hide some of the Vaio EEPROM data to non-root users.

Note to packagers:

* Perl scripts have been renamed to omit the trailing .pl (for example
  decode-dimms.pl is now named decode-dimms). I think it's more
  user-friendly that way.

Please help test this upcoming version of i2c-tools. You can get the
latest SVN snapshot from:
  http://dl.lm-sensors.org/i2c-tools/snapshots/

Thanks,
-- 
Jean Delvare

_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c

                 reply	other threads:[~2008-03-25 11:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20080325120421.71bb8977@hyperion.delvare \
    --to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
    --cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox