On 30 May 2017 at 19:19, Richard Purdie <richard.pur...@linuxfoundation.org> wrote: > > On Tue, 2017-05-30 at 12:00 -0400, Trevor Woerner wrote: > > On Tue, May 30, 2017 at 11:44 AM, Richard Purdie > > <richard.pur...@linuxfoundation.org> wrote: > > > > > > > > > > > Maybe this would be a better way forward? Enable it, always, in > > > > ./configure, > > > > add the patch to check for it in the code itself, then you can > > > > build > > > > for all > > > > the gallium targets (including swrast) and know that the patented > > > > code will > > > > only kick in where it's supported in hardware (and thus patent- > > > > safe)? > > > That sounds like exactly what we need to do! > > Okay. The only caveat being, if someone actually *wanted* to enable > > float for swrast, this would prevent them from going down that path. > > > > ajax on #dri-devel pointed out that some piglit tests go from pass to > > fail instead of being skipped as a result of the above patch since > > the > > piglit tests are done with swrast and run very poorly without float > > enabled. > > If someone really wants to enable it, they can drop the patch. I'm open > to feedback from others like Ross/Jussi but IMO I think we can accept > the degraded piglit results for swrast...
Sounds like a completely reasonable compromise to me. Jussi
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
