Help wanted: individual alarm files

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

 



Hi Gong Jun,

On Thu, 5 Jul 2007 19:27:40 +0800, JGong at winbond.com wrote:
> >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.

Great, thanks!

> 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.

I don't know, sorry. The only system I know using a W83791D is the Acer
Altos R300 server. Charles Spirakis (Cc'd) wrote the Linux 2.6 w83791d
driver, he should be able to tell you which system he was using.

-- 
Jean Delvare




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

  Powered by Linux