CreateBuffer/VAAPICreateBuffer.CreateBufferWithOutData/326 failed #89
Assignees
Comments
|
Yes, size should actually be the size of the actual buffer structure (i.e. |
|
a series of test case is related with the issue. ASSERT_STATUS(vaCreateBuffer(m_vaDisplay, m_contextID, bufferType, |
|
@XinfengZhang agree. I am working on patches now... |
uartie
added a commit
to uartie/libva-utils
that referenced
this issue
Jan 22, 2018
vaCreateBuffer needs the sizeof the actual buffer data structure associated with the buffer type, which could be profile specific. Previous test logic was passing the sizeof the buffer "type" enum, which is wrong. Fix the tests so that the correct buffer size is calculated based on profile specific buffer types. Several buffer types were removed from the previous test parameters since their size may be application specific, arbitrary, and/or require additional setup beyond the capabilities of the current buffer test cases. These rules will need to be fleshed-out and tests for them added later on. Fixes intel#89 Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com>
uartie
added a commit
to uartie/libva-utils
that referenced
this issue
Jan 23, 2018
vaCreateBuffer needs the sizeof the actual buffer data structure associated with the buffer type, which could be profile specific. Previous test logic was passing the sizeof the buffer "type" enum, which is wrong. Fix the tests so that the correct buffer size is calculated based on profile specific buffer types. Several buffer types were removed from the previous test parameters since their size may be application specific, arbitrary, and/or require additional setup beyond the capabilities of the current buffer test cases. These rules will need to be fleshed-out and tests for them added later on. Fixes intel#89 Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com>
uartie
added a commit
to uartie/libva-utils
that referenced
this issue
Jan 23, 2018
vaCreateBuffer needs the sizeof the actual buffer data structure associated with the buffer type, which could be profile specific. Previous test logic was passing the sizeof the buffer "type" enum, which is wrong. Fix the tests so that the correct buffer size is calculated based on profile specific buffer types. Several buffer types were removed from the previous test parameters since their size may be application specific, arbitrary, and/or require additional setup beyond the capabilities of the current buffer test cases. These rules will need to be fleshed-out and tests for them added later on. Fixes intel#89 Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com>
uartie
added a commit
to uartie/libva-utils
that referenced
this issue
Jan 29, 2018
vaCreateBuffer needs the sizeof the actual buffer data structure associated with the buffer type, which could be profile specific. Previous test logic was passing the sizeof the buffer "type" enum, which is wrong. Fix the tests so that the correct buffer size is calculated based on profile specific buffer types. Several buffer types were removed from the previous test parameters since their size may be application specific, arbitrary, and/or require additional setup beyond the capabilities of the current buffer test cases. These rules will need to be fleshed-out and tests for them added later on. Fixes intel#89 Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com>
Merged
uartie
added a commit
to uartie/libva-utils
that referenced
this issue
Jan 29, 2018
vaCreateBuffer needs the sizeof the actual buffer data structure associated with the buffer type, which could be profile specific. Previous test logic was passing the sizeof the buffer "type" enum, which is wrong. Fix the tests so that the correct buffer size is calculated based on profile specific buffer types. Several buffer types were removed from the previous test parameters since their size may be application specific, arbitrary, and/or require additional setup beyond the capabilities of the current buffer test cases. These rules will need to be fleshed-out and tests for them added later on. Fixes intel#89 Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com>
uartie
added a commit
that referenced
this issue
Jan 30, 2018
vaCreateBuffer needs the sizeof the actual buffer data structure associated with the buffer type, which could be profile specific. Previous test logic was passing the sizeof the buffer "type" enum, which is wrong. Fix the tests so that the correct buffer size is calculated based on profile specific buffer types. Several buffer types were removed from the previous test parameters since their size may be application specific, arbitrary, and/or require additional setup beyond the capabilities of the current buffer test cases. These rules will need to be fleshed-out and tests for them added later on. Fixes #89 Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
call vaCreateBuffer with such parameters (size = 4, num_elements=1, VAEncSequenceParameterBufferType), it return invalidate parameter , because size < sizeof(VAEncSequenceParameterBufferType)
The text was updated successfully, but these errors were encountered: