On 2002.05.28 09:26 Sergey V. Udaltsov wrote: > > Here's today's log, if someone wants to post it on the site. I might > be > > able to fill in some of the missing dates too, does someone have a list > of > > the missing ones? > Just one final question: will we have 2 implementations: secure and fast > or will there be something else (one fast and secure implementation). It > is not clear from the log. > > Cheers, > > Sergey >
I believe it's not clear - as it isn't evident for myself either. I think that evolution will be: - the _fastest_ implementation possible will be achieved in the very near future, after the DMA is fully functional. I think this is certain. - next the security _will_ be then addressed in order to the driver makes into a release. Depending on the work required / time available we might - do a secure implementation without many concerns with achieving _optimum_ speed or, - do the _optimum_ secure implementation - in a distant future the DRI architecture _may_ evolve to a different scheme were security towards the client is less tighten, i.e., it assumes that the client applications are secure and have been authorized by other way (e.g., user permissions, etc.) Note that there is alot of grey in here: - we don't know what's the performance impact of enforcing security in mach64 (and there are quite a few approaches to do that too) - we don't know if DRI will indeed evolve in that sense. My concern here is loosing too much time with enforcing security now to be later on put aside due to different assumptions. I hope that I have shed some light on this. Things will be more clear as time goes by, and all these "if's" will be discussed here again. Regards, Jos� Fonseca _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
