From: Ondrej Zary <linux@rainbow-software.org>
To: Karel Kulhavy <clock@twibright.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: I2C EEPROM write access
Date: Wed, 25 May 2005 17:09:01 +0200 [thread overview]
Message-ID: <4294950D.2000102@rainbow-software.org> (raw)
In-Reply-To: <20050525125609.GA15412@kestrel.twibright.com>
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
next prev parent reply other threads:[~2005-05-25 15:07 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 [this message]
2005-05-28 17:10 ` Jean Delvare
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=4294950D.2000102@rainbow-software.org \
--to=linux@rainbow-software.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