Hello all, I thank all those that have answered my questions, I still have a few more. Here goes.
I saw that geometry shaders were landed recently in some form. My questions are: * What is the execution style of the geometry shader on i965? (i.e. the fragment shader is invoked 8 fragments at a time and the vertex shader is invoked 2 vertices at a time). * what is the "geometry shader style" supported? i.e. are input/output blocks supported between stages, can inputs and outputs be declared as just "in type foo" and "out type foo"? Additionally are the layout() bits specifying the geometry shader input and output supported? Looking at the mesa-dev traffic, I am guessing it is the "older style" where layout is not in place and input and output blocks are not there yet, but I cannot tell. I know I was advised to not yet look at the GL dispatch function pointer thing, but I could not help myself; I saw that the functions are specified by .xml files which in turn generates some source code. Is there any movement to use the .xml registry from Khronons (at https://cvs.khronos.org/svn/repos/ogl/trunk/doc/registry/public/api/ )? I admit that this won't add any features really, but was thinking it might take some manual labor out of the function dispatch thing ... though it looks like the .xml from Mesa also has an ID field as well(I think to where the function is located in the dispatch table)... Last question set and I do not know a good way to go about this. Right now the documentation of Mesa looks like to me to be in the code in comments; this is great when working on one area/zone, but really hard to get a global picture of Mesa. Given that I am trying to do just that, I think it would be beneficial to produce some text for others to read. And now the icky questions and begging: * Given that I am new, my understanding is going to be incorrect at times and so I will need feedback from those that know for corrections. Additionally a feedback of open questions from people who are new (like me) or who are working in one area only would be useful to make sure the document is useful to more people than just me. However, I feel uneasy posting blobs of text that might be wrong to the mailing list out of fear of later google searches finding it... thoughts? * I would like to land this document into the Mesa repo eventually. An important question is what from shall the document take? I am leaning on the idea of doxygen pages and the doxygen files are in src/ so that when headers/sources get modified in a non-localized way the doxygen files have a hope to be modified too. My worry is that this adds more work to any implementation work or worse: the .doxy files rot anyways and now located in src/ . * Going further, assuming that this is wanted and it takes the form of .doxygen files, I would like to be adding doxygen group tags to header files so that navigation to modules and module categorization is also in the sources. Moreover, I want to generate -2- doxygen messes: one for developers to navigate code (i.e. include sources into the doxgen generated html and another which is header only). Tthe goal being that a developer can click through the code quickly to find where/how Mesa does something. and now a confession, I admit that I am mostly only interested in how it all maps down to i965; so.... I am not too sure how the uptake to other drivers or for that matter all of gallium will take place... -Kevin --------------------------------------------------------------------- Intel Finland Oy Registered Address: PL 281, 00181 Helsinki Business Identity Code: 0357606 - 4 Domiciled in Helsinki This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
