We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 3711 - update vendor check for accelerated OpenGL
Summary: update vendor check for accelerated OpenGL
Status: ASSIGNED
Alias: None
Product: SDL
Classification: Unclassified
Component: video (show other bugs)
Version: HG 2.0
Hardware: All Linux
: P2 enhancement
Assignee: Sam Lantinga
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-25 04:03 UTC by programmerjake
Modified: 2017-08-11 17:11 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description programmerjake 2017-07-25 04:03:28 UTC 
I noticed that the vendor check in ShouldUseTextureFramebuffer in SDL_video.c is way out of date.
It needs to have Intel, AMD, and several Mesa drivers added.
My vendor string for AMDGPU-PRO is "Advanced Micro Devices, Inc."
Comment 1 Ryan C. Gordon 2017-08-09 05:25:34 UTC 
(Sorry if you get a lot of copies of this email, we're touching dozens of bug reports right now.)

Tagging a bunch of bugs as target-2.0.6.

This means we're in the final stretch for an official SDL 2.0.6 release! These are the bugs we really want to fix before shipping if humanly possible.

That being said, we don't promise to fix them because of this tag, we just want to make sure we don't forget to deal with them before we bless a final 2.0.6 release, and generally be organized about what we're aiming to ship. After some debate, we might just remove this tag again and deal with it for a later release.

Hopefully you'll hear more about this bug soon. If you have more information (including "this got fixed at some point, nevermind"), we would love to have you come add more information to the bug report when you have a moment.

Thanks!
--ryan.
Comment 2 Sam Lantinga 2017-08-11 17:11:53 UTC 
Updated to look at post 2.0.6.

At this point can we just assume that this path is fast enough on all drivers?