I've attached an iic driver which is a modified version of the one by Dan Malek and Kim Jorgensen. Thanks for the initial effort. After many hours of trying different scenarios I've finally found the trick to the microcode patch. What you have to understand with the microcode path is that the parameter ram is relocated and you must initialize the Rx/Tx parameters manually (i.e. the init Tx/Rx command is not available due to the relocation). Info on the microcode patch can be found at http://www.mot.com/SPS/ADC/pps/subpgs/etoolbox/8XX/i2c_spi.html. Attached is the updated iic driver and a spi driver in development. The spi driver is from Matthew Locke over at Montevista. I've been working on this spi driver for quite a while and am having trouble with it in interrupt driven mode. I was wondering if anyone could look it over and see if I am doing something generally wrong. It is in slave mode and the device attached just takes data in (i.e. the Clock is always on, only the SMIMISO pin is connected and the Enable pin is always active). Any possible reasons why the "write" always times out would be appreciated. Thanks
-Dan Winkler Yahoo! Messenger - Talk while you surf! It's FREE. http://im.yahoo.com/ -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: iic.c Url: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20001016/b6febb79/attachment.txt -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: spi.c Url: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20001016/b6febb79/attachment-0001.txt
