Re: [Freeipmi-devel] sensor output issue

[Albert Chu]

> | Do you agree on this??
> `----
> Table 36.1, Event/Reading Type Code Ranges classifies "0x6F" as
> "Sensor-specific discrete" type. Such types *should only* refer
> "Table 36-3, Sensor Type Codes". 

So are you saying "HSC Drv X Pres (Drive Slot)" should still not be
displayed??

Al

--
Albert Chu
address@hidden
Lawrence Livermore National Laboratory

----- Original Message -----
From: Anand Babu <address@hidden>
Date: Wednesday, March 24, 2004 3:53 pm
Subject: Re: [Freeipmi-devel] sensor output issue

> ,----[ Albert Chu <address@hidden> ]
> | Hey AB,
> | 
> | The following sensors are not output unless the -vv option is 
> passed to
> | sensors.
> | 
> | HSC Drv X Status (Drive Slot)
> | HSC Drv X Pres (Drive Slot)
> | 
> | HSC Drv X Status has an event/read type code of 0x6F.  Table 36-3 
> of the
> | IPMI Spec doesn't list any info about Drive Slots.  So I believe
> | that one can be ignored.
> `----
> Yes you are correct.
> 
> ,----
> | But, HSC Drv X Pres has an event code of 0x08.  So this sensor 
> should| be output with either "Device Present" or "Device Absent" 
> (Table| 36-2).
> | 
> | I think the bug lies in the function 
> ipmi_is_sensor_reading_available().|  Currently, the function only 
> checks if the sensor type is
> | IPMI_SENSOR_TYPE_DRIVE_SLOT.  Instead, the function should check 
> if the
> | sensor type is IPMI_SENSOR_TYPE_DRIVE_SLOT and that the 
> event/read type
> | is == 0x6Fh.
> | 
> | Do you agree on this??
> `----
> Table 36.1, Event/Reading Type Code Ranges classifies "0x6F" as
> "Sensor-specific discrete" type. Such types *should only* refer
> "Table 36-3, Sensor Type Codes". 
> 
> Happy Hacking,
> -- 
> _.|_ 
> (_||_)
> Free as in Freedom <www.gnu.org>
>