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
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.faill...@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
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 mar...@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
IMHO all the red blocks should stand for not implemented. Whether $driver
could do it or not that is highly individual and depends on the
feature/extension and the actual hardware.
-Emil
P.S. I don't work on the radeon drivers.
On 05/09/14 20:54, Romain Failliot wrote:
So right now, if it's red
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.faill...@foolstep.com
Am 25.08.2014 07:56, schrieb Kenneth Graunke:
On Monday, August 25, 2014 12:05:07 AM Romain Failliot wrote:
Some folks helped me and a lot of detection bug have been fixed!
I have a question though (for my own culture): what's with the swrast, the
softpipe and the llvmpipe? Aren't they all
On Mon Aug 25 2014 05:05:07 GMT+0100 (BST), Romain Failliot wrote:
Some folks helped me and a lot of detection bug have been fixed!
I have a question though (for my own culture): what's with the swrast, the
softpipe and the llvmpipe? Aren't they all software drivers? What's the
difference
Could it be possible to add these drivers in the lists instead of me adding
some more exceptions in my code?
(I ask that mainly because I might have bug reports saying that softpipe is
green but it's never mentioned in the original file)
2014-08-25 10:28 GMT-04:00 Roland Scheidegger
Yeah I guess so. I think we were lazy updating GL3.txt for these
drivers, I'll whip up a patch.
Roland
Am 25.08.2014 16:41, schrieb Romain Failliot:
Could it be possible to add these drivers in the lists instead of me
adding some more exceptions in my code?
(I ask that mainly because I
Also I think some features that were added to soft/llvmpipe were
marked as swrast in GL3.txt.
Marek
On Mon, Aug 25, 2014 at 5:41 PM, Roland Scheidegger srol...@vmware.com wrote:
Yeah I guess so. I think we were lazy updating GL3.txt for these
drivers, I'll whip up a patch.
Roland
Am
Some folks helped me and a lot of detection bug have been fixed!
I have a question though (for my own culture): what's with the swrast, the
softpipe and the llvmpipe? Aren't they all software drivers? What's the
difference between all of them?
Thanks you!
2014-08-23 20:02 GMT-04:00 Marek Olšák
On Monday, August 25, 2014 12:05:07 AM Romain Failliot wrote:
Some folks helped me and a lot of detection bug have been fixed!
I have a question though (for my own culture): what's with the swrast, the
softpipe and the llvmpipe? Aren't they all software drivers? What's the
difference between
Hi!
I made a PHP script to have a better representation of the OpenGL
compliance of Mesa:
http://creak.foolstep.com/mesamatrix/
But I'm not sure about the signification of some lines.
When there is a DONE, with no parenthesis after, does it means it's done
for all the drivers?
And when there is
On Sat, Aug 23, 2014 at 5:59 PM, Romain Failliot
romain.faill...@foolstep.com wrote:
Hi!
I made a PHP script to have a better representation of the OpenGL compliance
of Mesa:
http://creak.foolstep.com/mesamatrix/
Cool. You may also be interested in
Cool. You may also be interested in
http://people.freedesktop.org/~imirkin/glxinfo/glxinfo.html which
takes a more pragmatic approach of just using whatever is reported by
glxinfo for various hardware for released mesa versions.
That is impressive!
Seems reasonable. You're just talking
It's not correct. For example, transform feedback shouldn't be listed for r300.
Marek
On Sat, Aug 23, 2014 at 11:59 PM, Romain Failliot
romain.faill...@foolstep.com wrote:
Hi!
I made a PHP script to have a better representation of the OpenGL compliance
of Mesa:
16 matches
Mail list logo
