Hi All, Extremely sorry for the disclaimer in previous mail. will take care from next time.
Regd my questions, I understood only one advantage of user space drivers, that is, a. any mistakes in user space will not effect entire system. I am very interested to know all the important pros/cons of user space/kernel space I2C drivers. I also understood that user space driver can not handle interrupts. So, how does the SMBALERT# be handled for the devices which support the same. Request you to provide some understanding for the questions in below mail too. Thanks in advance. Thanks & Regards, -- Srinivas R On Wed, Oct 8, 2008 at 3:40 PM, <[EMAIL PROTECTED]> wrote: > > > ------------------------------ > *From:* Srinivas Ramana (WT01 - PES - Peripheral(Techology)) > *Sent:* Tuesday, October 07, 2008 5:13 PM > *To:* 'i2c@lm-sensors.org' > *Subject:* Regd. i2c-dev and SMBALERT# > > Hi All, > > 1. I would like to know the advantages and disadvantages of user space > driver for I2C using i2c-dev, compared to the kernel mode drivers. > > 2. What happens if a driver is already bind to the device and application > tries to open/use it using i2c-dev? > > 3. My understanding on SMBALERT# is that it provides the I2C/SMBus device > to interrupt the host. > a. The driver for SMBALERT# is different from the adapter driver? > b. What kind of support is provided for SMBALERT# in current > kernels? > > Request your help in understanding the above. > > > Thanks & Regards, > -- Srinivas R >
_______________________________________________ i2c mailing list i2c@lm-sensors.org http://lists.lm-sensors.org/mailman/listinfo/i2c
