Hi Samium > There is one hopefully nice idea to help DRI developement. > The first and best thing to make a project successful is a good and > clean codebase. The second is a comprehensible set of docs in order to > attract more developers. > > Not that i have paid enough time to find anything, but i think that a > dia overview diagram of the overall structure/APIs would be extremely > nice. > > e.g. how XFree talks to DRM, what DRMs are supposed to provide, DMA > issues etc etc > > also examples could be very useful indeed...
You are correct, clean code is good, and I think DRI has that, good documentation is also important. The documentation is not as good / complete as it could be, however if its not there you'll have to write it, reading the source code is recomended. Liam ---- it depends ------------------------------------------------------- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
