| Bug ID | 102296 |
|---|---|
| Summary | R9 285 VCE corruption since drm/amdgpu/gmc8: use the vram location programmed by the vbios |
| Product | DRI |
| Version | DRI git |
| Hardware | Other |
| OS | All |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | DRM/AMDgpu |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | adf.lists@gmail.com |
Bit late with this, bisected on drm-next-4.13-wip R9 285 Tonga I am getting corrupted output from VCE encode, omx or vaapi since below commit. To re-produce this you need to use gstreamer and encode "fast and large" eg. 2160p from raw nv12. Slow things like ffmpeg or gst-vaapi without ! queue ! seem to hide the issue somewhat. 26d4ac55d2260f8685475b3f6e76e276a238cca7 is the first bad commit commit 26d4ac55d2260f8685475b3f6e76e276a238cca7 Author: Alex Deucher <alexander.deucher@amd.com> Date: Tue Nov 1 13:08:33 2016 -0400 drm/amdgpu/gmc8: use the vram location programmed by the vbios This makes mc programming much simpler in future patches. Since evergreen, the vbios has been programming the fb location to the proper vram size. The only reason to reprogram it would be to change the location.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
