Limitations with respect to hpi-b, Advancedtca mapping specification, Using hpi-b – Artesyn System Management Interface Based on HPI-B (Centellis CO 31kX-4100-2000-4410) (June 2014) User Manual

Page 40

Advertising
background image

Using HPI-B

System Management Interface Based on HPI-B (Centellis CO31kX/4100/2000/4410) User’s Guide

40

In case of OEM multi records, Artesyn HPI-B always assumes
DataType=SAHPI_TL_TYPE_BINARY and Language=SAHPI_LANG_UNDEF for the field on
which the API is being called.

Limited saHpiResourceResetStateSet() call
Artesyn HPI-B does not support Reset Action SAHPI_RESET_ASSERT.

Unsupported saHpiParamControl() call
Artesyn HPI-B does not support saHpiParamControl().

Unsupported resource event log
Artesyn HPI-B does not support resource event logs.

Unsupported Unicode character set
Artesyn HPI-B does not support the Unicode character set.

Unsupported annunciator functionality
Artesyn HPI-B does not support annunciator functionality. Our platforms do not have
these features.

Unsupported SaHpiIdrFieldAdd() and SaHpiIdrFieldAddById() call
Artesyn HPI-B does not allow adding field in an inventory area with the above APIs.
To add a new field, add a new OEM area and use the second field of the area.

4.2.2

Limitations with Respect to HPI-B AdvancedTCA Mapping

Specification

The following limitations apply with respect to the compatibility with the HPI-B-AdvancedTCA
mapping specification SAIM-HPI-B.01.01-ATCA. Note that these limitations apply to the
current and also to all future Artesyn HPI-B releases. There are no plans to implement these
features in the future.

Only physical slot numbers are supported
Artesyn HPI-B only supports physical slot numbers in entity paths

Only "shall" and "should" requirements are supported
Artesyn HPI-B only supports the "shall" and "should" requirements of the HPI-to-
AdvancedTCA mapping specification SAIM-HPI-B.01.01-ATCA. "May" requirements might
not be supported.

Advertising