sensord 2.8.2 on 2.6.0/ASUS chip - subclient problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The names of clients and the addresses of their subclients are "well known"
so in prog/sensors/main.c we just look for them (see that file for more info).
Your proposal to look for the string "subclient" will work equally well.
Feel free to submit a sensord patch to us using either technique.
mds

Greg KH wrote:
> On Sun, Jan 11, 2004 at 01:19:18PM +0300, Andrey Borzenkov wrote:
> 
>>I do not know if it is a sensord (should not attempt to read subclient) or 
>>kernel (does not provide sufficient information) problem. Subclient can be 
>>determined by its name:
>>
>>{pts/1}% for i in /sys/bus/i2c/devices/*
>>do
>>echo ${i:t}:$(<$i/name)
>>done
>>0-002d:as99127f
>>0-0048:as99127f subclient
>>0-0049:as99127f subclient
>>
>>Greg, this is supposed to be established convention now?
> 
> 
> I think so, yes.  I'll let the userspace people answer your other
> questions.
> 
> thanks,
> 
> greg k-h
> 
> 



[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux