Hi John, --- In [email protected], [EMAIL PROTECTED] wrote: > > well done geert, :) > > i am actually working on the beta2 this very moment and will test you > new driver tonight :-) i will have to dig into my components box to > find a 24c32... (i think i only have 24c04 :)
Just looked to the data specifications for the 24C01-C16 and those should not be a problem to use to try out the driver. The only difference is that the address is only one byte long with those devices in stead of 2 bytes (like for the 24C32). But you still need the repeated start functionality to access random locations for reading. So, similar behaviour compared to the 24C32. > > once we are ready with the new patch, i would like to ask you to write a > article on the acme site, on how to use the driver for a few scenarios. For sure I'm willing to do that! No problems at all. There are, for the moment, still a few useless printk() statements in, which I have already kicked out locally at my side. That doesn't influence, of course, the way the driver currently works, so you can still use the one currently in the .rar file to test things out. I will send you today the "clean" version of i2c.c to your private email address. If problems would arise, pls. feedback to me. !!! PS !!! Pls. take into account that this I2C driver is now working with dynamically allocated MAJOR numbers and that the device node on the FoxBoard is now located in /var/dev! But to use it, you can still use "open( "/dev/i2c"...", as if the device node was still located into /dev. But you know the story already, I guess. See my wiki page to read the details (http://www.gevawebsolutions.com/wiki/index.php?title=FB_General_Issues#Adding_a_dynamic_MAJOR_number:_the_steps_to_take...), since the make process is also changed for that. Otherwise, you will not be able to build the driver into the FB image. Best rgds, --Geert
