Driver call and TGSI IR Bytestream

Daniel Melo Jorge da Cunha <[email protected]>
Newsgroups gmane.comp.video.mesa3d.user
Message-ID <CANbfre6tPVxgGS+6ziWRcj0piF4W-nEpMLVwsuBHE0dk=uxdtw@mail.gmail.com>
Hi, I have 3 questions. Please be nice... I'm struggling myself...

Let's say I am in file src/gallium/auxiliary/cso_cache/cso_context.c.
So, there is a function call pipe->draw_vbo(pipe, info) in the
function cso_draw_vbo(...).

1- Is this function call (pipe->draw_vbo(pipe, info)) really calling,
for a NV30 driver, pipe->draw_vbo = nv30_draw_vbo? Or for other driver
like NVC0, is it really calling pipe->draw_vbo = nvc0_draw_vbo?

2- If it is so, how could (mesa3d? gallium3d? X? ddx? the responsible)
call the correct one for the correct driver?

3- Is the pipe and info arguments in the function call mentionated
the encoded TGSI IR Bytestream? If it is not, how and where is it
encoded?

_______________________________________________
mesa-users mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/mesa-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.