The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Karel Kulhavy <clock@twibright.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: I2C EEPROM write access
Date: Sat, 28 May 2005 19:10:39 +0200	[thread overview]
Message-ID: <20050528191039.6f2bfa96.khali@linux-fr.org> (raw)
In-Reply-To: <20050525125609.GA15412@kestrel.twibright.com>

Hi Karel,

Sorry for the delay.

> Is it possible to use some Linux I2C driver to program an I2C EEPROM,
> for example 24C16?

I don't think there is a driver for that. A driver isn't the only
solution to do that though.

> I have noticed only read-only access to "DIMM eeproms". Are they
> 24C16-alike?

The eeprom driver supports the 24C01, 24C02, 24C04, 24C08 and 24C16. In
other words, all models which can be read using SMBus read byte data
commands.

> Is there some reason why write driver is not present like users could
> inadvertently overwrite their DIMM eeproms?

Exactly.

> Do these eeproms have a protection against write?

Some have, but that's unrelated.

> I am mainly interested in an application where 24C16 is in-circuit
> connected to a PC and contents read and wrote (typically poking
> at firmware configuration of various devices).

You may want to look at the prog/eepromer directory of the lm_sensors
project. We have a set of user-space tools to write to EEPROMs of
various sizes. They rely on the i2c-dev driver as the user-space/kernel
interface.

-- 
Jean Delvare

      parent reply	other threads:[~2005-05-28 17:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-25 12:56 I2C EEPROM write access Karel Kulhavy
2005-05-25 15:09 ` Ondrej Zary
2005-05-28 17:10 ` Jean Delvare [this message]

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=20050528191039.6f2bfa96.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=clock@twibright.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox