Huh?
The i2c code now interacts to userspace through sysfs, not /proc
anymore. CaT is properly looking for his sensors in sysfs.
Here's what happens when looking through sysfs on my box running 2.5.69:
# find /sys/ | grep -i i2c
/sys/bus/i2c
/sys/bus/i2c/drivers
/sys/bus/i2c/drivers/lm75
/sys/bus/i2c/drivers/lm75/0-0048
/sys/bus/i2c/devices
/sys/bus/i2c/devices/0-0048
/sys/devices/pci0/00:1f.3/i2c-0
/sys/devices/pci0/00:1f.3/i2c-0/0-0048
/sys/devices/pci0/00:1f.3/i2c-0/0-0048/temp_input
/sys/devices/pci0/00:1f.3/i2c-0/0-0048/temp_min
/sys/devices/pci0/00:1f.3/i2c-0/0-0048/temp_max
/sys/devices/pci0/00:1f.3/i2c-0/0-0048/power
/sys/devices/pci0/00:1f.3/i2c-0/0-0048/name
/sys/devices/pci0/00:1f.3/i2c-0/power
/sys/devices/pci0/00:1f.3/i2c-0/name
Which is what should be showing up on CaT's machine (of the lm75 device
is on his hardware.)
Hope this helps,
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/