[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: I2C EEPROM handling 2.4.19 vs 2.4.20



That makes more sense. The i2c driver was updated in 2.4.20 to work
with the PCF8563 RTC. Would it be possible for you to test the driver
in 2.4.22? If that doesn't work I will take a look at it some day.

I have a theory about peripheral busses that says that the fewer
pins you have the more complicated it is to get it to work in
all cases. I2C and USB are good examples. 

/Mikael

-----Original Message-----
From: Szabo, Tamas [mailto:Tamas.Szabo@xxxxxxx.com] 
Sent: Monday, September 01, 2003 10:07 AM
To: 'Mikael Starvik'
Cc: dev-etrax
Subject: RE: I2C EEPROM handling 2.4.19 vs 2.4.20


Hi,

It seems there is a misread. I meant the problematical difference is in "i2c.c" not in "eeprom.c".

Anyway when I try "hwtesteeprom" it says can not read back from eeprom with v2.4.20 i2c.c but it works good with v24.19 of i2c.c

Sza2.

> -----Original Message-----
> From:	Mikael Starvik [SMTP:mikael.starvik@xxxxxxx.com]
> Sent:	Monday, September 01, 2003 9:26 AM
> To:	'Szabo, Tamas'; dev-etrax
> Subject:	RE: I2C EEPROM handling 2.4.19 vs 2.4.20
> 
> Hi,
> 
> It seams very strange that eeprom.c from 2.4.19 works while eeprom.c 
> from 2.4.20 doesn't work. The only difference is that
> 
> if (i2c_getack());
> {
>   break;
> }
> 
> has been changed to
> 
> if (i2c_getack())
> {
>   break;
> }
> 
> (which is obviously correct).
> 
> This should make read retries work. The only reason for the later to 
> fail would be if the eeprom never response with an ACK. Do you get the 
> debug printout "failed to read from eeprom?"
> 
> /Mikael
> 
> -----Original Message-----
> From: owner-dev-etrax@xxxxxxx.com">mailto:owner-dev-etrax@xxxxxxx.com] On 
> Behalf Of Szabo, Tamas
> Sent: Saturday, August 30, 2003 9:03 PM
> To: dev-etrax
> Subject: I2C EEPROM handling 2.4.19 vs 2.4.20
> 
> 
> Hello,
> 
> We own some devboard_lx. First I used linux-2.4.19 and the I2C eeprom 
> (built onto board) was working correctly. Than I started to use 
> linux-2.4.20 and the eeprom accessing (through /dev/eeprom) seemed to 
> unusable. After a perfunctory lookup into kernel source I replaced 
> 2.4.20 i2c.c with 2.4.19 version of i2c.c. Due to the change the 
> eeprom access is usable and seems to
> be correct.
> 
> Although I now that 2.4.20 shipped with axis82, is the I2C driver 
> works correctly with the new board?
> 
> Brgds,
> 
> Sza2.
> 
> 
> 
> **********************************************************************
> ****
> **
> *******************
> The information contained in this message or any of its attachments may be
> confidential and is intended for the exclusive use of the addressee(s).
> Any
> disclosure, reproduction, distribution or other dissemination or use of
> this
> communication is strictly prohibited without the express permission of the
> sender. The views expressed in this email are those of the individual and
> not necessarily those of Sony or Sony affiliated companies. Sony email is
> for business use only. 
> 
> This email and any response may be monitored by Sony United Kingdom 
> Limited.
> (gfd)
> **********************************************************************
> ****
> **
> *******************


***********************************************************************************************
The information contained in this message or any of its attachments may be confidential and is intended for the exclusive use of the addressee(s). Any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited without the express permission of the sender. The views expressed in this email are those of the individual and not necessarily those of Sony or Sony affiliated companies. Sony email is for business use only. 

This email and any response may be monitored by Sony United Kingdom Limited.
(6)
***********************************************************************************************