createsurface test case issue in libva-utils-v1.8
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- c
- Domain
- testing-qa
Research direction
Read the createsurface test case in libva-utils-v1.8 first, then compare its surface-size assumptions and attribute-list handling with the VA-API behavior described. Check the interaction with the Intel i965 driver. Done means determining whether the test or driver is responsible for the reported limitations and documenting the expected behavior.
Written by the indexing model from the issue text.
Description
Now,I have found some issues about createsurface test case,here is what I have found:
first, createsurface test case do not limit surface size in v1.8 because not all GPU surface support 16x16 or 10240x10240
second,create surface with attribs will first query surface attribs and then create surface with these attribs
but maybe VASurfaceAttribIPixformat type attrib will have different value like this:
attrib_list={
{
......
VASurfaceAttribPixformat ,
VA_SURFACE_ATTRIB_SETTABLE,
value0
},
{
VASurfaceAttribPixformat ,
VA_SURFACE_ATTRIB_SETTABLE,
value1
},
{
VASurfaceAttribPixformat ,
VA_SURFACE_ATTRIB_SETTABLE,
value2
},
.....
}
but intel i965 driver just will get the last VASurfaceAttribPixformat value while calling createsurface and it is value2,so any issue in test case or intel driver?
- Dominant language
- C
- Stars
- 244
- Forks
- 175
- Avg merge
- 9d 7h
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from intel/libva-utils
-
av1encode: reference_frames[2..7] left as surface 0 (memset only covers 8 bytes)Possibly taken @0z5a claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
intel/libva-utils#390 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
intel/libva-utils#387 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
intel/libva-utils#378 · 6 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
intel/libva-utils#376 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
intel/libva-utils#374 ·
All issues in intel/libva-utils
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
[LOGO] VentoOSOpenlogo request
Difficulty 1/5 Under an hour Newbie friendliness 80/100
fastfetch-cli/fastfetch#2742 ·
Maintainers usually reply within 1 day
-
ecs_ptr_from_json does not free the buffer of a string longer than 256 bytes on two error pathsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SanderMertens/flecs#2444 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100