All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: Python bindings to i2c-dev
Date: Thu, 19 May 2005 06:25:28 +0000	[thread overview]
Message-ID: <20041229145938.095251f1.khali@linux-fr.org> (raw)
In-Reply-To: <20041229050526.GA5431@jupiter.solarsys.private>

Hi Mark,

> After a couple false starts and some hair-pulling, here is a Python
> module which allows SMBus access through the I2C /dev interface.  I
> would like to eventually add this to the lm_sensors project.
> 
> 	http://members.dca.net/mhoffman/sensors/python/

Maybe you could start with a link from the lm-sensors' site, either in
the news or on the useful addresses page?

> Which reminds me...  Khali: Is i2c-dev safe (ruin-proof) for people
> with IBM laptops?  Or would that check need to be built in to this?

It isn't safe. Single quick writes to addresses 0x54-0x57 are likely to
kill IBM laptops (it actually depends on what command is ran next). That
said, at the moment i2c-piix4 won't load on supposedly vulnerable
systems, so it shouldn't happen.

I have plans to replace quick writes (for detection) by byte reads for
this address range in Linux 2.6's i2c_detect/i2c_probe, just like I did
in i2cdetect and sensors-detect already, but it doesn't address the
i2c-dev issue. Maybe we can hack i2c-dev to prohibit quick writes to the
eeprom range entirely? That way all user-space tools would automatically
be safe.

-- 
Jean Delvare
http://khali.linux-fr.org/

  reply	other threads:[~2005-05-19  6:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  6:25 Python bindings to i2c-dev Mark M. Hoffman
2005-05-19  6:25 ` Jean Delvare [this message]
2005-05-19  6:25 ` Mark Studebaker
2005-05-19  6:25 ` Mark M. Hoffman
2005-05-19  6:25 ` Mark M. Hoffman

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=20041229145938.095251f1.khali@linux-fr.org \
    --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.