Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262228AbVEYNA3 (ORCPT ); Wed, 25 May 2005 09:00:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262268AbVEYNA3 (ORCPT ); Wed, 25 May 2005 09:00:29 -0400 Received: from [83.76.35.193] ([83.76.35.193]:50256 "EHLO kestrel.twibright.com") by vger.kernel.org with ESMTP id S262228AbVEYNAZ (ORCPT ); Wed, 25 May 2005 09:00:25 -0400 Date: Wed, 25 May 2005 14:56:09 +0200 From: Karel Kulhavy To: linux-kernel@vger.kernel.org Subject: I2C EEPROM write access Message-ID: <20050525125609.GA15412@kestrel.twibright.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Orientation: Gay User-Agent: Mutt/1.5.8i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 768 Lines: 22 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< - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/