[Mesa-dev] The GL3.txt format

Marek Olšák maraeo at gmail.com
Fri Sep 5 13:14:34 PDT 2014


Like Emil said, it depends on the feature. For example, the r300
hardware can do GL_ARB_clip_control from GL 4.5, but cannot do
GL_EXT_texture_array from GL 3.0. The driver doesn't support
GL_ARB_clip_control yet.

Marek

On Fri, Sep 5, 2014 at 9:54 PM, Romain Failliot
<romain.failliot at foolstep.com> wrote:
> So right now, if it's red it really means that the r300 could do it, but
> it's not been implemented yet?
>
>
> 2014-09-05 11:12 GMT-04:00 Marek Olšák <maraeo at gmail.com>:
>
>>
>> A lot of GL3 and GL4 features actually only require GL2 hardware and
>> r300 should support them.
>>
>> Marek
>>
>> On Fri, Sep 5, 2014 at 4:57 PM, Romain Failliot
>> <romain.failliot at foolstep.com> wrote:
>> > Hi guys!
>> >
>> > Little recap on my project. I don't know if've been there recently but
>> > there
>> > has been some nice changes (thanks for the llvmpipe and softpipe cleanup
>> > by
>> > the way).
>> > http://creak.foolstep.com/mesamatrix/
>> >
>> > I'm wondering if something could be done for the r300 status. I think it
>> > will definitely be red since it's not possible for these GPU to handle
>> > these
>> > extensions. Am I right?
>> > If I find a nice solution that doesn't bloat up the text file, would it
>> > be
>> > alright for you?
>> >
>> > Cheers,
>> > Creak
>> >
>> > 2014-08-25 15:13 GMT-04:00 Marek Olšák <maraeo at gmail.com>:
>> >>
>> >>
>> >> Also I think some features that were added to soft/llvmpipe were
>> >> marked as swrast in GL3.txt.
>> >>
>> >> Marek
>> >>
>> >
>
>


More information about the mesa-dev mailing list