Re: sensors vs 2.6

[Gene Heskett]

On Tuesday 09 December 2003 05:33, Sebastian Kaps wrote:
>Hi Gene!
>
>On Tue, 9 Dec 2003 02:58:01 -0500 you wrote:
>> kernel, 2.6.0-test11, and have dilligently searched the /proc and
>> /sys directories, and seem to have come up blank.
>
>I have configured "I2C support", "I2C device interface", "Intel
> PIIX4" and "Winbond ...". I get all sensor readings in
> /sys/bus/i2c/devices/*, e.g.:

I have this:
-----------------------
[root@coyote linux-2.6]# grep I2C .config
# I2C support
CONFIG_I2C=y
CONFIG_I2C_CHARDEV=y
# I2C Algorithms
CONFIG_I2C_ALGOBIT=y
# CONFIG_I2C_ALGOPCF is not set
# I2C Hardware Bus support
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_I810 is not set
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_PHILIPSPAR is not set
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_PROSAVAGE is not set
# CONFIG_I2C_SAVAGE4 is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
CONFIG_I2C_VIA=y
CONFIG_I2C_VIAPRO=y
# CONFIG_I2C_VOODOO3 is not set
# I2C Hardware Sensors Chip support
CONFIG_I2C_SENSOR=y
----------------
and this:
-----------------
[root@coyote linux-2.6]# grep SENSORS .config
# CONFIG_SENSORS_ADM1021 is not set
CONFIG_SENSORS_EEPROM=y
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM85 is not set
CONFIG_SENSORS_VIA686A=y
CONFIG_SENSORS_W83781D=y
---------------------
set for a Biostar M7VIB mobo.  It all works for 2.4.

No errors were noted during the build other than the advansys 
deprecated "check_region" calls that have been noted here previously.

But:
--------------------
[root@coyote linux-2.6]# tree /sys/bus/i2c/devices/
/sys/bus/i2c/devices/
|-- 0-0050 -> ../../../devices/pci0000:00/0000:00:09.0/i2c-0/0-0050
|-- 0-0051 -> ../../../devices/pci0000:00/0000:00:09.0/i2c-0/0-0051
|-- 0-0052 -> ../../../devices/pci0000:00/0000:00:09.0/i2c-0/0-0052
|-- 0-0053 -> ../../../devices/pci0000:00/0000:00:09.0/i2c-0/0-0053
|-- 0-0054 -> ../../../devices/pci0000:00/0000:00:09.0/i2c-0/0-0054
|-- 0-0055 -> ../../../devices/pci0000:00/0000:00:09.0/i2c-0/0-0055
|-- 0-0056 -> ../../../devices/pci0000:00/0000:00:09.0/i2c-0/0-0056
|-- 0-0057 -> ../../../devices/pci0000:00/0000:00:09.0/i2c-0/0-0057
|-- 0-0061 -> ../../../devices/pci0000:00/0000:00:09.0/i2c-0/0-0061
|-- 1-0050 -> ../../../devices/pci0000:00/0000:00:11.0/i2c-1/1-0050
`-- 1-0051 -> ../../../devices/pci0000:00/0000:00:11.0/i2c-1/1-0051

11 directories, 0 files
-----------------------
And ALL of that is related to the various eeproms in the system.  
Mostly on my bt979 card.

To back out and do a tree on /sys/devices gets me 171 directories and 
583 files, none of which are named 'input_fan1'.

So obviously something didn't get built, and it looks like its the 
winbond stuff.  The question is why?  Is there some method that can 
be used to interrogate the kernel and determine if the stuff is 
actually in there?

>,----
>
>| # cat /sys/bus/i2c/devices/0-002d/fan_input1
>| 5400
>
>`----

No such subdir in the devices dir...

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
99.22% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.

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