Results 1 to 3 of 3

Thread: Inconsistency between specification and header files

  1. #1
    Junior Member
    Join Date
    Jul 2007
    Posts
    1

    Inconsistency between specification and header files

    Dear Sir or Madam:

    I am writing to ask you OpenMAX IL 1.1 specification.

    I saw OpenMAX IL 1.1 specification(openmax_il_spec_1_1.pdf) and
    header files(omx_il_v1_1_headers.zip) to implement an IL core and
    Components. I have found out five functions which is inconsistent
    with their arguments between the specification and the header files.
    Could you please tell me which is the formal specification?

    The five functions which is inconsistent with the arguments:
    (1). OMX_GetComponentsOfRole()
    PDF:
    OMX_API OMX_ERRORTYPE OMX_GetComponentsOfRole (
    OMX_IN OMX_STRING role,
    OMX_INOUT OMX_U32 *pNumComps,
    OMX_INOUT OMX_U8 *compNames)
    OMX_Core.h:
    OMX_API OMX_ERRORTYPE OMX_GetComponentsOfRole (
    OMX_IN OMX_STRING role,
    OMX_INOUT OMX_U32 *pNumComps,
    OMX_INOUT OMX_U8 **compNames)

    (2). OMX_GetRolesOfComponent()
    PDF:
    OMX_API OMX_ERRORTYPE OMX_GetRolesOfComponent (
    OMX_IN OMX_STRING compName,
    OMX_INOUT OMX_U32 *pNumRoles,
    OMX_OUT OMX_U8 *roles)
    OMX_Core.h:
    OMX_API OMX_ERRORTYPE OMX_GetRolesOfComponent (
    OMX_IN OMX_STRING compName,
    OMX_INOUT OMX_U32 *pNumRoles,
    OMX_OUT OMX_U8 **roles)

    (3). (*GetComponentVersion)()
    PDF:
    OMX_ERRORTYPE (*GetComponentVersion)(
    OMX_IN OMX_HANDLETYPE hComponent,
    OMX_OUT OMX_STRING pComponentName,
    OMX_OUT OMX_VERSIONTYPE* pComponentVersion,
    OMX_OUT OMX_VERSIONTYPE* pSpecVersion)
    OMX_Component.h:
    OMX_ERRORTYPE (*GetComponentVersion)(
    OMX_IN OMX_HANDLETYPE hComponent,
    OMX_OUT OMX_STRING pComponentName,
    OMX_OUT OMX_VERSIONTYPE* pComponentVersion,
    OMX_OUT OMX_VERSIONTYPE* pSpecVersion,
    OMX_OUT OMX_UUIDTYPE* pComponentUUID)

    (4). (*UseEGLImage)()
    PDF:
    OMX_ERRORTYPE (*UseEGLImage)(
    OMX_IN OMX_HANDLETYPE hComponent,
    OMX_INOUT OMX_BUFFERHEADERTYPE** ppBufferHdr,
    OMX_IN OMX_U32 nPortIndex,
    OMX_IN OMX_PTR pAppPrivate,
    OMX_void* pBuffer)
    OMX_Component.h:
    OMX_ERRORTYPE (*UseEGLImage)(
    OMX_IN OMX_HANDLETYPE hComponent,
    OMX_INOUT OMX_BUFFERHEADERTYPE** ppBufferHdr,
    OMX_IN OMX_U32 nPortIndex,
    OMX_IN OMX_PTR pAppPrivate,
    OMX_IN void* eglImage)

    (5). (*ComponentRoleEnum)()
    PDF:
    OMX_ERRORTYPE (*ComponentRoleEnum)(
    OMX_OUT OMX_STRING cRole,
    OMX_IN U32 nNameLength,
    OMX_IN OMX_U32 nIndex)
    OMX_Component.h:
    OMX_ERRORTYPE (*ComponentRoleEnum)(
    OMX_IN OMX_HANDLETYPE hComponent,
    OMX_OUT OMX_U8 *cRole,
    OMX_IN OMX_U32 nIndex)


    Truly yours.


    Kobayashi

  2. #2
    Junior Member
    Join Date
    Oct 2007
    Posts
    2
    OpenMAX IL 1.1.1 was recently released on Sept 9 that addresses the issues you have identified.

    The new specification document, errata and updated headers files are all available on the OpenMAX link on the Khronos site

  3. #3
    Junior Member
    Join Date
    Sep 2007
    Location
    bangalore
    Posts
    5
    http://www.khronos.org/developers/specs/


    is the link for OpenMAX IL 1.1.1 Specification

Similar Threads

  1. Discrepancy in specification and header files.
    By manojtharwani in forum OpenMAX IL
    Replies: 0
    Last Post: 06-25-2007, 10:35 PM
  2. Replies: 2
    Last Post: 01-01-1970, 12:00 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •