RE: [Lcd4linux-devel] Re: fixes to the i2c patch that Luis suppli ed

[Luis.F.Correia <Lui...@se...>]

Hi! 

> -----Original Message-----
> From: Michael Reinelt [mailto:re...@eu...] 
> Sent: Tuesday, April 05, 2005 9:42 AM
> To: lcd4linux-devel
> Subject: Re: [Lcd4linux-devel] Re: fixes to the i2c patch 
> that Luis suppli ed
> 
> Sorry for the first post, hit the wrong button :-)
> 
> >>on my 2.6.11 kernel :-)
> > Are you absolutely sure that that's your running kernel?
> 
> Yes, I am. Absolutely very shure.
> 
> > In my Fedora system, the source can be looked at
> > /lib/modules/(kernel-version)/build
> > if i'm not mistaken...
> I'm using debian, but none of the debian kernels, but my own vanilla
> homebrew kernel 2.6.11 from kernel.org.
> 
> > Anyway, you must have something broken over there, I just 
> don't know what...
> Yes, there *is* something broken here. It has something to do with the
> i2c.h file. It includes lots of other files, which should be used only
> when compiling the kernel.
> 
> A ugly workaround would be to extract the needed symbols from 
> i2c.h and
> hardcode them into drv_generic_i2c. But, as I said, ugly ugly ugly....
> 
> Is there any other sowftware out there which uses the i2c subsystem? I
> once had a look into lm_sensors, but they do not really use the i2c
> interface, but the various files in /proc or /sys only.

Well, to be able to talk with I2C devices, some drivers must be present.
lm_sensors does use i2c interface, in fact they were the originators of
the current I2C support in Linux.

But I really don't have an answer to your particular problem. I'll ask my
other Linux co-workers for possible workarounds...

> 
> bye, Michael
> 
> -- 
> Michael Reinelt <re...@eu...>

Luis Correia