Hi, I just want to say that you did a great job. I just found your driver too late because i improved a little bit the one which is on the wiki web site of axis (http://developer.axis.com/wiki/doku.php?id=contributions). However, you can see there, the solution i used to implement the write-read ioctl () command. Personnaly, i like the "file" way that associate an i2c chip to a file, it's more UNIX style and useful. Best regards
--- In [email protected], "Geert Vancompernolle" <[EMAIL PROTECTED]> wrote: > > Hi, > > As I mentioned a while ago (see thread > http://tech.groups.yahoo.com/group/foxboard/message/3020), I was busy > studying and possibly trying to improve the current version of the I2C > driver. > > Well, I've just finished reworking the I2C driver. The changes are > quite drastical. The changes result in a faster driver and now it can > cope with all possible cases (at least, the ones that I know of...). > > The driver has been tested on several I2C components (see further) and > there are more to come... > > I've created a zip file that contains the following items: > > - a PDF file describing the changes, showing DSO plots and giving in > detail the timings of the current I2C implementation. > > - a new I2C error header file i2c_errno.h (see PDF file for some > explanation) > > - the changed i2c.h header file > > - the changed etraxi2c.h header file > > - the new I2C source file > > - an example file which has been used to test the I2C driver on the > following devices: > * NVM 24C32 > * PCF8574 > * PCF8591 > > - Makefile to use for the example code. > > - switches header file to activate one or more of the tested components. > > Those interested can have a look over here: > > http://tech.groups.yahoo.com/group/foxboard/files/GeertVc > > All suggestions/improvements/remarks are welcome. > > I would especially ask John Crispin to have a look at the driver (John > knows what I'm talking about...) > > > Best rgds, > > --Geert >
