Motorola Coldfire I2C driver patch

[Uwe Kindler]

Hello Andrew, hello Bart,

attached is a patch for Bart's Coldfire I2C device driver that is still 
(after 8 months) not part of the eCos CVS. I submitted the I2C device 
driver in October 2005.

Now already other developers start to ask me about the I2C driver 
because they found my I2C driver from October 2005 in the eCos patches 
archives. I sent Bart's I2C driver to Rainer Arndt because he asked me 
about the driver. He uses the driver with a number of I2C devices (not 
only one single device like me) and sent me the following patch for 
Bart's version of the I2C driver.

This is what he said about the patch:

"If a single byte is read from a missing device, the function 
cyg_i2c_transaction_rx returned 1 and 0xFF as data because after sending 
the addres byte the missing ACK was not detected. So the missing evice 
was not detected"

It would be easier to provide patches if the driver would be part of the 
CVS. I understand that Bart don't want to bring a buggy I2C device 
driver into the CVS. But if it need's such a long time then maybe it 
would be better to have the driver in the CVS and give other people a 
chance to fix these bugs. We already use the driver in a final product 
(only 1 I2C device) and Rainer Arndt uses the driver with a number of 
I2C devices.

I know that a Coldfire port and device drivers are part of the 
commercial eCos Pro version from eCosCentric. Is this the reason that 
you don't include the driver into the official eCos repository?

Kind Regards, Uwe

Uwe Kindler
Software Engineering

--

cetoni GmbH
Am Wiesenring 6
D-07554 Korbussen

Tel.: +49 (0) 36602 338 28
Fax:  +49 (0) 36602 338 11
uwe.kindler@cetoni.de
http://www.cetoni.de
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: i2c_mcf52xx.c.patch
URL: <http://sourceware.org/pipermail/ecos-patches/attachments/20060705/eec4f55b/attachment.ksh>