X hits on this document

PDF document

February 10, 2006 - page 121 / 238

615 views

0 shares

0 downloads

0 comments

121 / 238

7.7. FRU DATA

109

i n t i p m i _ e n t i t y _ d e a c t i v a t e ( i p m i _ e n t i t y *ent, _ t i p m i _ e n t i t y _ c b d o n e ,

void

* c b _ d a t a ) ;

is used.

7.6.4

Auto Activation and

Deactivation

Some systems allow the system management software to specify a policy to execute when a device is inserted or a removal is requested. Basically, the time from an activate request to when an activation is automatically started can be specified. The time from a deactivate request to when an deactivation is automatically started can be specified. The following functions can be used to read and update these times:

i n t i p m i _ e n t i t y _ g e t _ a u t o _ a c t i v a t e _ t i m e ( i p m i _ e n t *ent, i t y _ t i p m i _ e n t i t y _ t i m e _ c b h a n d l e r ,

void

* c b _ d a t a ) ;

i n t i p m i _ e n t i t y _ s e t _ a u t o _ a c t i v a t e _ t i m e ( i p m i _ e n t *ent, i t y _ t i p m i _ t i m e o u t _ t a u t o _ a c t , i p m i _ e n t i t y _ c b d o n e ,

void

* c b _ d a t a ) ;

i n t i p m i _ e n t i t y _ g e t _ a u t o _ d e a c t i v a t e _ t i m e ( i p m i _ e n t *ent, i t y _ t i p m i _ e n t i t y _ t i m e _ c b h a n d l e r ,

void

* c b _ d a t a ) ;

i n t i p m i _ e n t i t y _ s e t _ a u t o _ d e a c t i v a t e _ t i m e ( i p m i _ e n t *ent, i t y _ t i p m i _ t i m e o u t _ t a u t o _ d e a c t , i p m i _ e n t i t y _ c b d o n e ,

void

* c b _ d a t a ) ;

The timeouts are standard OpenIPMI time values, which are in nanoseconds. These will return ENOSYS if the operation is not supported. They will return EINVAL if the time is out of range. To disable auto- activation and deactiviation, the time may be set to IPMI_TIMEOUT_FOREVER. To cause the transitions to o c c u r i m m e d i a t e l y , s e t t h e v a l u e t o I P M I _ T I M E O U T _ N O W .

7.7

FRU Data

OpenIPMI supports fetching all the FRU data supported by the IPMI spec, as well as SPD data in DRAMs. It also supports plugins for handling other types of FRU data that can be provided for OEM data. It is able to fetch and modify all the standard data and all the custom data stored in multi-records and has a multirecord decoder plugin interface with the standard multirecords implements, along with some ATCA record decoders. SPD data (and other data types, unless they provide their own interfaces) can only be decoded. Standard FRU data specified by the IPMI spec can be decoded and written.

7.7.1

Reading

FRU Data

The FRU data interface has two separate interfaces fetching data data from a FRU data object. One is a generic interface that works with all FRU data type, including SPD or OEM data. The other is an IPMI-specified FRU interface that only works with the FRU data format specified by IPMI.

Document info
Document views615
Page views615
Page last viewedWed Dec 07 15:24:47 UTC 2016
Pages238
Paragraphs8090
Words85809

Comments