[Mesa-dev] mesa state tracker geometry shader bits

Roland Scheidegger sroland at vmware.com
Wed Oct 16 00:39:55 CEST 2013


Am 15.10.2013 21:15, schrieb Dave Airlie:
> On Tue, Oct 15, 2013 at 7:58 PM, Jose Fonseca <jfonseca at vmware.com> wrote:
>> ----- Original Message -----
>>> Hi,
>>>
>>> I pulled Brian's patches and then hacked llvmpipe locally to claim GL 3.2,
>>> and ran piglit, fixed some of the obviously missing pieces and crashes.
>>>
>>> These aren't immediately going to expose any new functionality, but it
>>> might help if someone doing r600g or nouveau support can concentrate on their
>>> driver.
>>>
>>> Any objections to pushing them?
>>
>> Sounds great to me.  The more testing llvmpipe gets the better.  Thanks for doing this.
> 
> It seems to pass nearly as many as Paul reported for Ivybridge, the
> fails seems to be in the generic code anyways.
>>
>>
>> Actually, if things are not too broken, I'd really would like to get llvmpipe to advertise 3.2 out of the box.  It would imply lying about MSAA of course, but I think that that would be acceptable (and even preferable) for a SW renderer.
> 
> If people agree I'd like to do that as well, anyone got any objections
> to initially lying about softpipe and llvmpipe? for 3.2 depth clip
> disable and seamless cube map would be needed on top of the two
> multisample extensions.

We are working on the other two (though for depth clip disable I'm not
sure wrt differences to d3d10) so that would fit well. Maybe better to
stick to 3.1 until that has landed however (I'd be happy to lie about
seamless filtering, which probably if not supported any app would just
ignore anyway, but advertizing depth clip disable and then ignoring it
could probably give unexpected results).

Roland


More information about the mesa-dev mailing list