On Thu, Jun 27, 2002 at 04:35:16PM -0600, Brian Paul wrote: [...] > >Just curious: do you guys have a plan for moving the mach64 code into the >trunk? Are there any major issues that need to be resolved first? >
In my perspective the major issues missing are: 1. Make sure the new DMA model works well in all configurations (at this moment it seems that only PPC remains with problems) 2. Vertex buffer template custumized to the Mach64 hardware format (this isn't major but I wanted to work this first before addressing security, because it can change radically how we do it, and I'm finishing it). 3. The security - this is the real issue that must be addressed before a merge with the trunk (and therefore, being ready for a release). >BTW, I took a stab at updating the http://dri.sourceforge.net/doc/cvs.html >page which lists and describes the current CVS branches. > >The mach64 branch is described as: > > > This is the branch for the ATI Rage Pro driver development. The work is > > unfunded and is only just beginning, so a working driver is still a long >way > > off. Please do not ask when it will be complete. This branch also >contains some > > DRM architectural changes, designed to make writing new drivers easier and > > remove significant amounts of duplicated code. > >Maybe this should be updated. > Yep. This is way old (I think it refers to mach64-0-0-1-branch). José Fonseca ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Bringing you mounds of caffeinated joy. http://thinkgeek.com/sf _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
