If it's OK to sacrifice some speed in order to make the mach64 driver secure and elegible to go the the trubk then there is quite a simple solution: disable DMA by default (using the MMIO pseudo-DMA). Users still have the option to force DMA in XF86Config if they so wish.
I think this would make most people happy, as users no longer had to download snapshots, and for the developers it would be easier too as no further HEAD merges would be necessary. The mach64 will only be secure with a redesign of the DRM DMA engine. Without it there will always be a tradeoff between speed to get security. Jose Fonseca On Mon, Feb 09, 2004 at 11:59:37AM -0800, James Jones wrote: > Dave, > > 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 ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
