[Mesa-dev] [PATCH v3 0/9] Gallium Nine

Henri Verbeet hverbeet at gmail.com
Wed Nov 19 04:50:14 PST 2014

On 19 November 2014 00:26, Emil Velikov <emil.l.velikov at gmail.com> wrote:
> From a quick look at MSDN it seems to me that going the DDI (like) route
> would require substantial rework on the wine side. How much contribution
> from wine can we expect ? Would you have the chance to help with
> design/coding, or would you be (no disrespect here) limited to answering
> questions ?
Yeah, it would require a significant amount of work on the wined3d
side as well, which is part of the reason we'd like to make sure that
work can't be avoided.

> I'm sure that not everything in mesa is perfect yet I've not seen (m)any
> bug reports from you guys. If/when you guys spot something
> broken/extremely slow please bugzilla it or send an email to the ML.
I think for a part that's because I prefer sending patches when time
allows. E.g. around 2010-2011 I sent a couple of patches, mostly for
making the Wine tests pass on r600c and later r600g. These days the
amount of time I can spend on Mesa is more limited, but at least r600g
generally works pretty well for me. I know Stefan regularly runs tests
on r300g and r600g and sends bug reports when something breaks.

> Speaking of feedback, please consider using GLX_MESA_query_renderer. It
> should help you (at least a bit) with the massive
> vendor/device/video_memory tables that you currently have.
It's already on our (unfortunately fairly large) todo-list.

More information about the mesa-dev mailing list