I was the one that brought this up. I have a little time (a few hours a week only) to work on it, and since no one else seemed to care I was going to tackle this very slowly. I was going to work on the DRM insecurities once I dug up the old conversations with Jose detailing what needed to be done. I know he had a whole new dma system in the works that was supposed to be flexible enough to solve these problems. I was hoping to come up with a simpler fix to get things working just good enough for mach64 to be considered secure. I assumed it could then be included in the main branches (wherever they may be now) where it would be easier to keep up to date at least.
I'm glad others are still interested and its good to hear that progress is already being made.
-James
Dave Airlie wrote:
I noticed it came up during the IRC meeting this week about moving the mach64 up to the top of tree,
So how should this be done in terms of CVS, the mach64 driver as is insecure, so I'd rather not put into an official tree until those issues are sorted out, I know Jose has some ideas on these and I'll see if I can track him down at some point, but for now I'd like to bring the current branch up to the top of tree at least,
So should I use the mesa tip and start a new mach64 branch on the DRI tree or should I make a branch on both trees?
oh yeah I'm unsure who brought it up on IRC so if you are on the list speak up :-)
Dave.
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
