[openbeos] Re: Mesa - OpenGL

The biggest issue is drivers.
Be's driver methodology is different than (and, IMHO, better than) Linux's.
Secondly, hardware acceleration is not an all or nothing game. If it were,
things would be much easier. For example, if there were a video card
that accepted a bytecode form of OpenGL. Then, there would be little
for a driver writer to do, and hw opengl would take a few days to write.
The issues with hw opengl, as I understand it (and I could be wrong) are:
1) understanding and unifying the functionality that video cards have
2) implementing fast software solutions for the "default" - i.e. if a card 
desn't have bump mapping, do it in software.
3) map openGL calls to 1.

There looks to be a fair amount more to incorporating DRI than just implementing
an API in app_server. First off, you would need to use Linux drivers. Ugh.
Secondly, there is kernel level support. Not to mention the shared memory area.

It seems to me to be an idea that would make OBOS far from Be-like.
In any case, the compact answer would *resoundingly* be, not in R1.

>Hi,
>
>I just wanted to point to the recent Mesa 4.0.1 release which brings 3d 
>hardware acceleration for a wide variety of graphics chipsets to Linux 
>using XFree's DRI API.
>(see http://dri.sourceforge.net )
>
>It looks like implementing the DRI API in the app=5Fserver is a good idea 
>and would lead to a OpenGL 1.3 conform API in OpenBeOS, including 
>hardware acceleration.
>
>Is DRI taken into account for the Interface Kit Team=3F
>
>Adios...
>   Axel.
>
>
>
>

Other related posts: