All of lore.kernel.org
 help / color / mirror / Atom feed
* I2C EEPROM write access
@ 2005-05-25 12:56 Karel Kulhavy
  2005-05-25 15:09 ` Ondrej Zary
  2005-05-28 17:10 ` Jean Delvare
  0 siblings, 2 replies; 3+ messages in thread
From: Karel Kulhavy @ 2005-05-25 12:56 UTC (permalink / raw)
  To: linux-kernel

Hello

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

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

Is there some reason why write driver is not present like users could
inadvertently overwrite their DIMM eeproms? Do these eeproms have a
protection against write?

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).

CL<

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: I2C EEPROM write access
  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
  1 sibling, 0 replies; 3+ messages in thread
From: Ondrej Zary @ 2005-05-25 15:09 UTC (permalink / raw)
  To: Karel Kulhavy; +Cc: linux-kernel

Karel Kulhavy wrote:
> Hello
> 
> Is it possible to use some Linux I2C driver to program an I2C EEPROM,
> for example 24C16?
> 
> I have noticed only read-only access to "DIMM eeproms". Are they
> 24C16-alike?

SPD EEPROMs on DIMMs are 24C02.

> Is there some reason why write driver is not present like users could
> inadvertently overwrite their DIMM eeproms? Do these eeproms have a
> protection against write?

The SPD EEPROMs should not be write protected - that's what 
specification says - so probably are not.

> 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).
> 
> CL<

-- 
Ondrej Zary

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: I2C EEPROM write access
  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
  1 sibling, 0 replies; 3+ messages in thread
From: Jean Delvare @ 2005-05-28 17:10 UTC (permalink / raw)
  To: Karel Kulhavy; +Cc: linux-kernel

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2005-05-28 17:10 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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.