[Mesa-dev] RFC: per-driver extension lists

[Benjamin Bellec]

Hi,

Correct me if I'm wrong, it looks like EXT_draw_buffers2 (OpenGL 3.0) is
not enabled on Radeon HD2900 (R600 codename) due to hardware limitation.
I have no R600 card to check glxinfo.

David Airlie enabled this extension with this commit:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=de48199693484fc903627ce53b007901af2e37a8

And current code is still:
/* Supported except the original R600. */
    case PIPE_CAP_INDEP_BLEND_ENABLE:
    case PIPE_CAP_INDEP_BLEND_FUNC:
        /* R600 doesn't support per-MRT blends */
        return family == CHIP_R600 ? 0 : 1;


Regards.

Benjamin Bellec

Le 28/03/2014 22:38, Aaron Watry a écrit :
> On Fri, Mar 28, 2014 at 10:32 AM, Ilia Mirkin <imirkin at alum.mit.edu> wrote:
>> On Fri, Mar 28, 2014 at 11:14 AM, Aaron Watry <awatry at gmail.com> wrote:
>>>> Do people have opinions on whether it'd be useful to also gather data
>>>> for older hardware? FWIW I threw my TNT2 in there, which is probably
>>>> among the oldest hw supported by mesa.
>>>>
>>> I'm not sure if it's worthwhile or not, but if you want/need it, I've
>>> got a Radeon x1950 at home that I can pop in for a r300g run.
>> I'm uncertain of the usefulness, but if you give it to me, I'll throw
>> it up there.
> I'll give it a run on a spare system later. Probably mesa 10.1, but
> I'll have to see what's installed on that machine when I get home.
>
>>>> Any other suggestions? As a reminder, the current list is available at
>>>> http://people.freedesktop.org/~imirkin/glxinfo/glxinfo.html (defaults
>>>> to core context, so older stuff doesn't show up, click on 'compat' to
>>>> see it).
>>>>
>>> I like the UI in general, the one suggestion that I have at the moment
>>> is to split <div id="table"> into two divs.  Anchor the driver
>>> names/generations to the top of the window (position:fixed) and allow
>>> the table content to continue to be scrolled.  That way you always
>>> have the card names at the top of your screen.  You'll probably need
>>> to add a dynamically-sized spacer to the top of the 2nd div, but I'll
>>> leave that as an exercise to the reader.
>> Good idea. One problem with position:fixed is that it doesn't
>> (didn't?) work on mobile browsers. I'll give it a shot though.
> Ahh, yeah...  I haven't tried it on mobile...  I spend my days doing
> desktop web software, not mobile. If it works, great, if not, then
> it's not the end of the world..
>
>>   -ilia
> _______________________________________________
> mesa-dev mailing list
> mesa-dev at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/mesa-dev