Hi Valentin,
On 10/14/2014 04:21 PM, Valentin Longchamp wrote:
> Hi Matthias,
>
> On 10/14/2014 02:32 PM, Matthias Fuchs wrote:
>> Hi Valentin,
>>
>> my patch fixed environment from i2c eeprom. I am not sure on which board
>> I ran into that trouble. Probably PMC440. So reverting my former patch
On Thu, Oct 23, 2014 at 04:15:24PM +0200, Matthias Fuchs wrote:
> Hi Valentin,
>
> On 10/14/2014 04:21 PM, Valentin Longchamp wrote:
> > Hi Matthias,
> >
> > On 10/14/2014 02:32 PM, Matthias Fuchs wrote:
> >> Hi Valentin,
> >>
> >> my patch fixed environment from i2c eeprom. I am not sure on whic
Hi Valentin,
On 10/14/2014 04:21 PM, Valentin Longchamp wrote:
> Hi Matthias,
>
> On 10/14/2014 02:32 PM, Matthias Fuchs wrote:
>> Hi Valentin,
>>
>> my patch fixed environment from i2c eeprom. I am not sure on which board
>> I ran into that trouble. Probably PMC440. So reverting my former patch
Hi Matthias,
On 10/14/2014 02:32 PM, Matthias Fuchs wrote:
> Hi Valentin,
>
> my patch fixed environment from i2c eeprom. I am not sure on which board
> I ran into that trouble. Probably PMC440. So reverting my former patch
> will break environment in i2c eeprom again on many boards.
Good that y
On 10/14/2014 03:01 PM, Holger Brunck wrote:
> On 10/14/2014 02:32 PM, Matthias Fuchs wrote:
>> Hi Valentin,
>>
>> my patch fixed environment from i2c eeprom. I am not sure on which board
>> I ran into that trouble. Probably PMC440. So reverting my former patch
>> will break environment in i2c eepr
On 10/14/2014 02:32 PM, Matthias Fuchs wrote:
> Hi Valentin,
>
> my patch fixed environment from i2c eeprom. I am not sure on which board
> I ran into that trouble. Probably PMC440. So reverting my former patch
> will break environment in i2c eeprom again on many boards.
>
> But perhaps there's a
Hi Valentin,
my patch fixed environment from i2c eeprom. I am not sure on which board
I ran into that trouble. Probably PMC440. So reverting my former patch
will break environment in i2c eeprom again on many boards.
But perhaps there's a better way to fix that.
Matthias
On 10/14/2014 11:16 AM,
Since i2c_init_all always sets the bus back to CONFIG_SYS_SPD_BUS_NUM
for compatibility reasons, it means that any eeprom not located on this
CONFIG_SYS_SPD_BUS_NUM is not accessible with the eeprom commands, even
if you change the bus number with an i2c dev command before.
Furthermore i2c_init_al
8 matches
Mail list logo