On Mon, Mar 22, 2010 at 1:29 PM, LiYe <omni.l...@gmail.com> wrote: > I'm interested in openGL implementation and the DRI driver development. > Specifically, I want to learn how an OpenGL command was implemented and > how it was converted into direct rendering context and transferred to > the hardware. I know this is a quite complicated and time-consuming > task, but it would be great if I can start the learning cruve with my > newbie background. So I'm trying to look into the mesa codes. However, > it seems quite large and monolithic and I cannot find a suitable > breaking point. So I wrote this to ask for some experienced advice. For > an overview of how DRI works in codes(not in theory as explained in > documents), where should I start with?
I would suggest getting an IDE that has decent code browsing capabilities (I personally like to play with the KDevelop4 beta even though it's still a bit flaky) and just start stepping through your favourite driver in a debugger. Note that your life will be less painful if you have a second machine from which you can SSH in, so that your gdb session doesn't live on the same X server as the OpenGL application that you're debugging. cu, Nicolai ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
