From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?ISO-8859-1?Q?Andreas_Bie=DFmann?= <andreas.devel@googlemail.com>
Date: Wed, 27 Nov 2013 15:50:29 +0100
Subject: [U-Boot] OMAP3 i2c issues on IGEP, u-boot 2013.10
In-Reply-To: <CAFqH_50_aaOutrL_iEs4JbQgRbsbaej_7eDuz+yBXQoaE8wejQ@mail.gmail.com>
References: <20131127131929.34505e23@skate>	<CAFqH_539GUrz34anUp4d-kFarcGnxfeCZiufg8ZjkF+G_s6dUA@mail.gmail.com>	<20131127151121.51f124e6@skate>
	<CAFqH_50_aaOutrL_iEs4JbQgRbsbaej_7eDuz+yBXQoaE8wejQ@mail.gmail.com>
Message-ID: <529606B5.6080905@gmail.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

Dear Enric Balletbo Serra,

On 11/27/2013 03:22 PM, Enric Balletbo Serra wrote:
> 2013/11/27 Thomas Petazzoni <thomas.petazzoni@free-electrons.com>:
>> On Wed, 27 Nov 2013 14:56:15 +0100, Enric Balletbo Serra wrote:
>>> 2013/11/27 Thomas Petazzoni <thomas.petazzoni@free-electrons.com>:
>>>> We've recently updated from u-boot 2013.04 to u-boot 2013.10 on our
>>>> IGEP boards (OMAP3 based, U-Boot shows "OMAP36XX/37XX-GP ES1.2"), and
>>>> we're seeing random I2C communication problems at startup.
>>>
>>> Right, I've reproduced the issue. Any OMAP3-based board affected for
>>> this issue ?
>>
>> Not sure to understand your question: my paragraph above mentions the
>> IGEP board as being the platform on which I'm seeing this. So indeed, a
>> OMAP3-based board is affected. But maybe I misunderstood your question.
>>
> 
> Oops, sorry, bad question :)
> 
> Anybody knows if other OMAP3-based boards are affected for this issue ?

not here on tricorder board, it has an AM37xx core.

Best regards

Andreas Bie?mann