lkml.org 
[lkml]   [2003]   [Apr]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.5.66: The I2C code ate my grandma...
On Sat, Apr 05, 2003 at 10:59:50AM +1000, CaT wrote:
> On Fri, Apr 04, 2003 at 09:14:24AM -0800, Greg KH wrote:
> > So if you disable the I2C config items, everything works just fine?
>
> Yup.
>
> > I did send out a bugfix for the i2c code for a problem in 2.5.66, it's
> > now included in the latest -bk tree. Could you grab that patch and see
> > if it fixes your problem?
>
> Ok. Running -bk10. Where, umm, is the userspace interface to it? I can't
> find anything in /proc or /sys so I can't see if it's actually working.
> Incase they're useful here are snippets from .config and dmesg:

To a:
tree /sys/bus/i2c/devices/
to see all of the i2c devices in your system.
Then go in to the directories of those devices to see the sensor values
for the devices.

libsensor support will be forthcoming soon for these changes.

> One question. Will I need ISA support in the kernel for this?

Depends, did you need it before? :)
I didn't change any of that logic, just where the information the
sensors report has moved locations.

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:34    [W:0.443 / U:0.560 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site