Help wanted: individual alarm files

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

 



Hi Jean,

>The future libsensors assumes that all hardware monitoring drivers
>follow the standard sysfs interface defined in
>Documentation/hwmon/sysfs-interface. They all mostly do already, except
>for one thing: alarms. Most drivers are still only exposing a single
>file with all alarms in a bit-vector, in chip-dependent order. In order
>to let the new libsenors display the alarms properly, we must add
>individual alarm files to these drivers. For some drivers, fault and/or
>beep files need to be added too.

I'd like to take care of w83792d chip's converting work. It will be
finished in the next week.

And could you please give me some information about the ASUS motherboard
with w83791d chip using for hardware monitor function? 

Any help will be welcome.

Best regards,
Gong Jun


===========================================================================================
The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such  a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Winbond is strictly prohibited; and any information in this email irrelevant to the official business of Winbond shall be deemed as neither given nor endorsed by Winbond.




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

  Powered by Linux