On 2/21/07, Erik Mouw <mouw@xxxxxxxxxxxx> wrote:
On Wed, Feb 21, 2007 at 10:56:36PM +0530, Sandeep Sanjay Patil wrote: > AFAIK, i2c chip will have an i2c address, using which u communicate with > the chip on i2c bus. Correct, but the linux i2c drivers take care of that. > And, the chip might also expect data to arrive in a particular manner, > so... if you want to connect it to a different bus that i2c, probably > the chip also needs to support that bus.. eg. SPI etc. Again, the linux i2c drivers take care of endianess problems. What the OP wanted to know is how he could communicate with an I2C device, which is only possible through an I2C adapter. The parport I2C adapter Rene suggested is such a device.
Just to be sure about the parport suggestion - The driver I will write will be regular I2C driver, right ? it will work unchanged on any I2C bus, especially on a real I2C bus in an embedded platform ? Thank You naziir
Erik -- They're all fools. Don't worry. Darwin may be slow, but he'll eventually get them. -- Matthew Lammers in alt.sysadmin.recovery -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF3IaP/PlVHJtIto0RAk2kAJ98hfUJ/nLxFziaI0ZgUjGm3VCsjQCeOK0V tzjWKQuX5+HMtbi1iiCiYes= =Bh3A -----END PGP SIGNATURE-----
-- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
