From: <li...@ba...> - 2007-02-19 11:31:14
|
Hi! Jon Smirl "jon...@gm..." wrote: [...] >> One reason I would like to keep the drivers as kernel modules is that you >> can use tools like mode2 or xmode2 to easily test them. > These should be able to work with a user space library that provides > the right API. And you are volunteering to implement that? ;-) > I was already to try and merge these drivers into the kernel, but now > I am having second thoughts about doing a user space implementation > instead. Ok. [...] >> I don't know about GPIO, but for the I2C driver a userspace driver also is >> available, but I did not have time to integrate it into the code base yet. > All of the parallel, serial, gpio, i2c type devices probably have to > go into the kernel because they need to do accurate timings. Once you > are in user space it becomes difficult to time things. > > For example the user space implementation for i2c (I2C_CHARDEV) still > bit twiddles in the kernel and then only presents you with the > results. Yes, but the all LIRC related parts can be in user space in case of the I2C driver. Christoph |