Results 1 to 2 of 2

Thread: Call execution of SendCommand took longer than limit

  1. #1
    Junior Member
    Join Date
    Apr 2008
    Posts
    2

    Call execution of SendCommand took longer than limit

    Hi:
    I have implemented some decoder component, and there is not theread in these component, so the component do deocde action when IL Client invoke OMX_FillThisBuffer() or OMX_EmptyThisBuffer() or OMX_SendCommand(). but while conformance test, there are some warning message as "Call execution of SendCommand on OMX.xxxx.avcencode took longer than limit: Limit=5 ms Actual=6 ms". Can these components pass conformance test?

  2. #2
    Member
    Join Date
    May 2008
    Location
    California, USA
    Posts
    51

    Re: Call execution of SendCommand took longer than limit

    Quote Originally Posted by lxh_df
    there are some warning message as "Call execution of SendCommand on OMX.xxxx.avcencode took longer than limit: Limit=5 ms Actual=6 ms". Can these components pass conformance test?
    Yes. The spec uses "should" for timing, which is a recomendation.

    IL 1.1.1 section 3.2:
    When a time limit for the execution of a method is specified, it is not intended as a hard restriction for the conformance of the component to the standard, but if the limit is not respected, a note shall appear in the description document related to the component.
    Thanks,

    Roger
    Roger Nixon, Broadcom Corporation

Similar Threads

  1. Why does EGL call glGetIntegerv when I call wglSwapBuffer?
    By teriba in forum Cross API and window system integration
    Replies: 0
    Last Post: 07-23-2009, 04:50 AM
  2. Replies: 1
    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
  •