Originally posted by dungeon
View Post
Announcement
Collapse
No announcement yet.
Threaded GL Dispatch Code For Mesa Sent Out For Review
Collapse
X
-
By sending it through the review process at least those interested can check it and if they feel that strongly they can point out specific issues they have, which in turn can be handled.
sounds like Marek wants to merge so more people can easily test like us and provide appropriate bug reports. Seems reasonable.
- Likes 3
Comment
-
Originally posted by smitty3268 View Post
The slippery slope is having a bunch of complicated, unmaintained, poorly tested code in master, that's what. It's a slope because 1 thing like this is fine, but 10? Or 50? That's when trouble is bound to happen.
It does not affect anything by default and it is disabled by default, so why not
Comment
-
Originally posted by debianxfce View Post
Who cares, Amd workers have fixed kernel and mesa driver bugs in a week or two. Nobody has such resources that can test with every game and hardware configuration. Add there hundreds of Linux distributions, you will get the picture.
Anyway, nobody is saying things have to be exhaustively tested. But when glxgears is broken, it shouldn't be that tough to figure out.
Comment
-
Originally posted by smitty3268 View PostBut they usually develop it in a separate branch until at least glxgears is working.
Some apps won't see any improvment (these should be skipped), some should see something by default or just in certain settings scenario, some will get worse perf, some should see segfaults... that is what people should expect from enabling this and that it is normalLast edited by dungeon; 09 February 2017, 04:09 AM.
Comment
-
He, he, people better to follow what Marek said there and test only with GL3 apps exclusively for the beggining, even among these it won't work for everything... basically don't expect it should do anything for anything else
Apps based on OpenGL 3.3 Core should work. Some OpenGL 4.x apps might work too, but it's not certain. There is a lot of work to do.
Comment
-
I think there is consent that the code shouldn't be abandoned just because it's not in a perfect shape. On the other hand I also think that it's very reasonable not to implement a white list with specific names on in universal driver code for some features.
So as long as it stays an option to be enabled by the user so he gets better performance but is disabled for all games by default not many people would disagree, I'm quite sure about that.
But the code itself should also be commented being ugly and the specific feature should be handled on a list of ugly parts for people that like to contribute to the drivers in my opinion. Perhaps there could also be a bug report for every case that describes the issue so the list can link to it.
If it's not done this way I'm afraid it will never reach an acceptable state to work for all cases.Last edited by oooverclocker; 09 February 2017, 04:31 AM.
Comment
-
Originally posted by oooverclocker View PostOn the other hand I also think that it's very reasonable not to implement a white list with specific names on in universal driver code for some features.
https://cgit.freedesktop.org/mesa/me...i/common/drirc
If you wanna Unigine to not work, etc... just remove drirc and you will be proper.
With AMDGPU-PRO just don't install 'libgl1-amdgpu-pro-appprofiles' package and you will be again proper
Or with FGLRX just uncheck this box and you will be proper
Last edited by dungeon; 09 February 2017, 04:47 AM.
Comment
Comment