kas1e wrote:@Gregor [quote] As i see in Mesa it classed as EVERGREEN, so probably Caicos was marketed as Northern Islands/R900, but internally it still Evergreen, and still fits into r600.
Is it works for you with AEON's RadeonHD driver ? I mean warp3dnova/ogles2/etc ? If yes, then i can enable it.
Unfortunately warp3dnova does not support Caicos. HD77xx is the oldest one.
we already use VA-API for hardware decode (va.library). For real video acceleration through Mesa we still need:
Bind a VA surface / friend BitMap as a GLES texture with no CPU copy (EGLImage-style). YUV / multi-plane textures (NV12/YV12 or documented planes + shader), not RGBA upload every frame. Stable MakeCurrent on that drawable across resize. Without that, Mesa can only glTexSubImage from RAM — presentation, not acceleration. Decode stays in va.library; Mesa would only need to show the surface as a texture.
Can you add this to mesa.library?
MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne x5000/40 AmigaOs4.1 FE
@kas1e was the libGL_mesa.a compiled with DWARF 5 or something?
I keep on getting errors like:
/opt/ppc-amigaos/lib/gcc/ppc-amigaos/11.3.0/../../../../ppc-amigaos/bin/ld: Dwarf Error: found dwarf version '5', this reader only handles version 2, 3 and 4 information.
/opt/ppc-amigaos/ppc-amigaos/SDK/local/newlib/lib/libGLU_mesa.a(quad.o): In function `gluCylinder':
quad.c:(.text+0x6ac): undefined reference to `glNormal3f'
/opt/ppc-amigaos/lib/gcc/ppc-amigaos/11.3.0/../../../../ppc-amigaos/bin/ld: Dwarf Error: found dwarf version '0', this reader only handles version 2, 3 and 4 information.
quad.c:(.text+0x71c): undefined reference to `glNormal3f'
/opt/ppc-amigaos/lib/gcc/ppc-amigaos/11.3.0/../../../../ppc-amigaos/bin/ld: Dwarf Error: found dwarf version '17181', this reader only handles version 2, 3 and 4 information.
quad.c:(.text+0x778): undefined reference to `glTexCoord2f'
I'm trying to compile my program that references libGLU (that I have re-compiled to theoretically work with your headers but could be screwing something up).
@davec555 libGL_mesa.a ? I only have LibGL.a and it was compiled with 11.3.0. And same as libSDL_mesa.a was compiled the same, but you better now compile you own version from Capehil's sources. libGLU you need to recompile too if need it.
@kas1e yes I meant the mesa version of libgl.a. I had compiled my own sdl2 and glu but when trying to link I got those errors. As I hadn't compiled the libgl.a (mesa) I thought the dwarf differences might have been from that... I had previously compiled my own libglu.a from source for gl4es and didn't have a problem. Trying to work out what us different here.
@kas1e I am in desperate need of help. I was able to handle compiling libGLU previously with GL4ES (as the src also came from ptitSeb), but I can't for the life of me compile that with your headers. Any chance you could build a libGLU or point me to a compatible version that shares your mesa includes?
Thanks Dave
Edit: Nevermind. I downloaded another GLU repository (in case ptitSeb's was gl4es specific), and compiled that. Still had errors and decided to try changing the order of the -lGL and -lGLU (so -lGLU was first), and low and behold my app linked successfully. Weird as the with miniGL and gl4es -lGL was first.