I've fixed most of the problems in 2385, but the problem still remains
in omx. Could someone who's familiar with omx please take a look?
Alternatively, maybe we can try adding -fcommon to just omx, until this
issue is resolved.
On Tue, 2020-01-21 at 18:49 +0100, Bas Nieuwenhuizen wrote:
> I think
Should we make iris the default for 20.0? I think it's time. Sadly,
gitlab milestones don't let you comment on them.
On Wed, Jan 22, 2020 at 12:26 PM Dylan Baker wrote:
> Hi list, due to some last minute changes in plan I'll be managing the 20.0
> release. The release calendar has been updated
On Thu, Jan 23, 2020 at 9:44 AM Jason Ekstrand wrote:
>
> Should we make iris the default for 20.0? I think it's time. Sadly, gitlab
> milestones don't let you comment on them.
It does seem like it's time to flip that switch.
___
mesa-dev mailing lis
Dear all,
has anybody any objections if I merge the r600/NIR code?
Without explicitely setting the debug flag it doesn't change a thing,
but it would be better to continue developing in-tree.
Best,
Gert
___
mesa-dev mailing list
mesa-dev@lists.fre
Hello,
As most of you know, we've been developing a new 3D driver called 'iris'
for recent Intel hardware (Gen8+), based on the Gallium driver framework
used by the rest of the Mesa community. After two years of development,
we think that it's ready for production, and recommend it as the default
