On Wed, Jan 14, 2015 at 5:16 PM, Michael Cronenworth <mike(a)cchtml.com> wrote:
On 01/14/2015 06:28 AM, Jaroslav Reznik wrote:
> * Contingency mechanism: Revert and try to do in next release
I don't see this one happening. The patch set is large. Upstream has
rejected it. The affected user base is small. I'm unconvinced right now that
it's worth the time and effort to maintain.
I will cite Axel Davy who wrote
this patchset (he sent this privately
to me, you and other maintainer)
1) you can find a list of D3D11 only apps here:
As you can see all d3d11 apps before 2012 had a d3d9 backend, and some
d3d11 apps still had
a d3d9 backend after that. A lot of new games released this year (most
non-big production games) are still using d3d9.
2) After several discussions with wine devs, they said they would
never consider putting us upstream,
but that we could with - a lot of work and refactoring - compile our
mesa code with the wine compiler and get a resulting d3d9.dll that we
could distribute and give to users so that they can use it instead of
This scheme requires work, and we would like to let the possibility to
have nine outside of wine. It's probably not going to happen in the
next two years, but who knows...
3) wine nine code doesn't change a lot of wine code. Most of the ~20
patches are on our code.
Our team take care of rebasing often under the last version of wine.
4) Do you play some games with wine ? Some games have severe issues,
like stutter, etc. While on radeon cards, there is obvious gains, on
nouveau there is too according to one of our nouveau tester.
I think for fedora it would make sense to keep the mesa nine package,
but I'm not 100% sure for the wine part.
We are probably going to have PlayOnLinux support soon, which allows
to install easily different version of wine, including non-official
ones. Users wanting to use wine nine could go through that if it isn't
shipped in the main wine package.