Re: new device driver features

This is not as simple as it looks. There is only one standalone I2C driver for
Linux, the Voodoo one.  Maxtrox and Radeon both have their I2C drivers bundled
into their framebuffer drivers. I2C support is a Linux 2.6 feature. Also,
loading Matrox/Radeon FB drivers to get I2C support reintroduces the mess of
having two device drivers trying to control a single piece of hardware.

I2C drivers are not very hard to write in user space and they have already all
been written in the Xfree code. We could start off with the existing user space
ones and switch to kernel level ones later.

How is I2C done on BSD?


--- Keith Packard <[email protected]> wrote:
> 
> Around 14 o'clock on Nov 14, Alex Deucher wrote:
> 
> > Also, for i2c, do we want to use the kernel interfaces or re-implement
> > in our lib?  I suppose it depends on if the kernel supports i2c.  linux
> > does, not sure about the bsds.
> 
> One of my main goals is to avoid reimplementing work which should (and is) 
> done elsewhere.  It seems like i2c is a general system service, therefore 
> we should select an appropriate interface and require it; perhaps 
> encouraging or supporting the deployment of that interface on systems not 
> yet doing so.  Replicating functionality available on most systems to 
> avoid requiring it on all systems is a ridiculous waste of time.
> 
> -keith
> 
> 


=====
Jon Smirl
jonsmirl-/[email protected]

__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree