On Sad, 2004-09-11 at 01:47, Vladimir Dergachev wrote: > One driver per device. I.e. one driver per *physical* device.
This is a religion the kernel doesn't follow. Its a pointless religion > Lastly, one point that you appear to have missed: DRM does DMA transfers > (among everything else). FB sets video modes - i.e. messes with PLL. > The problem is that there are configurations where messing with PLL while > a DMA trasfer is active will lock up PCI (or AGP) bus hard. Yes its a co-ordination issue. If the IDE disk writes to the bus the same moment as the IDE CD shit also happens. > For example, a video decoder can be clocked off pixel clock for video pass > through mode. If we trasfer video data to main RAM at the same time and > FB gets a command instructing it to change resolution there would be a > hard lockup. Gosh, just like if the IDE disk driver changes the bus clocking during an IDE CD transfer. You need co-ordination not some horrible glue it all together and pray hack. Thats always going to be true, and since you can do it without glueing it all together you might get somewhere by keeping them apart, otherwise I see no future. Most DRI users don't want FB, most FB users don't care about DRI or want to control the DRI from the fb side. Alan ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
