I am trying to understand DRI source, now from start, i.e. from OpenGL calls.
I was analizing file: lib/GL/glx/g_render.c, if I understand correctly there is stream build there, but where it's readed?
For example in glColor3f there is identifier: X_GLrop_Color3fv. I grep whole DRI source and can't find where it's used. So how stream decoder knows which opcode is it?
I was browsing documentation on dri.sf.net, but I am unable to find answer for
my question: "which functions in hardware driver (like lib/GL/mesa/src/drv/r200) are called
for given GL call?".
There are a couple levels of indirection that you're not seeing here. There is a set of "stub" functions for each GL call that redirect to either direct rendering functions (supplied by the DRI driver) or the indirect rendering functions (what you see in lib/GL/glx).
In the case of the direct rendering functions, the actual function that gets called by the stub can be changed at virtually any time depending on the GL state.
For the indirect functions, the opcode processing is done by the X server. That's what makes them indirect. :) Look in programs/Xserver/GL/glx to see how that is done. Notice that there is two versions of everything. This is to handle the case where the X server and the client have a different byte-ordering (i.e., the X server is on x86 and the client is on PowerPC).
------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
