> > > > 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:
Don't bother trying to get a global picture of mesa, pick small pieces of functionality and learn about them adding an extension is a good way to start learning, pick one of the smaller ones, grep for where previous extensions are implemented and plugged in, look at the git history. I don't think anyone who works on mesa started from a high level global understanding, its just too big. Dave. _______________________________________________ mesa-dev mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/mesa-dev
