From mboxrd@z Thu Jan  1 00:00:00 1970
From: York Sun <yorksun@freescale.com>
Date: Mon, 17 Sep 2012 22:57:54 -0500
Subject: [U-Boot] [PATCH] common/i2c: Add i2c write command
In-Reply-To: <20120917233643.GC17195@bill-the-cat>
References: <1347818550-7660-1-git-send-email-yorksun@freescale.com>
	<20120917221638.GA17195@bill-the-cat>
	<0n5xu0e95foaei04c6ynfgyu.1347924535509@email.android.com>
	<20120917233643.GC17195@bill-the-cat>
Message-ID: <5057F142.80001@freescale.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On 09/17/2012 06:36 PM, Tom Rini wrote:
> On Mon, Sep 17, 2012 at 11:29:00PM +0000, sun york-R58495 wrote:
>
>> Tom,
>>
>> It's like eeprom write but it writes to general devices, not specificly to system eeprom. I would have to use i2c mw command a lot without this.
>
> Right.  I guess what I'm getting at is, are you writing to some sort
> of other device or writing bits to storage attached to i2c?  Does it
> really not make sense to just use 'eeprom write' even if it's not
> technically for The System EEPROM but rather some storage (or a number
> of storage chips) attached via i2c?
>
> I'm not objecting to i2c write mind you, I was wishing for something
> like this when I stumbled on CONFIG_CMD_EEPROM which did what I needed.
>

Tom,

I have a case under debugging where I need to use i2c write to devices. 
One device (EEPROM) has two-byte address length and most others 
(including other EEPROMs) have one byte address length. I also have 
other non-storage devices but I wouldn't use "i2c write" because "i2c 
mw" will be sufficient. eeprom command has its limitation for the case 
of variable device address and variable address length.

York