W dniu 18 marca 2010 17:40 użytkownik Alex Deucher <alexdeuc...@gmail.com> napisał: > 2010/3/18 Rafał Miłecki <zaj...@gmail.com>: >> W dniu 18 marca 2010 10:05 użytkownik Rafał Miłecki <zaj...@gmail.com> >> napisał: >>> Whoops, I missed one patch. My mistake. >> >> I've just applied all patches dated as "17-Mar-2010 22:42" and tested. >> >> Now memory reclocking is really enabled, but it causes corruptions for >> me. Maybe that's the same thing you experienced with dual head? >> >> Video is *far* from perfect, but maybe will give you some idea of what >> do I experience: >> http://estudent.put.poznan.pl/rafal.milecki/kernel/MOV00225.MP4 >> >> The same happened for me before all your patches, when I tried to >> enable memory reclocking on my own. > > yeah, the similar to what I saw with dualhead. I guess we are either > missing the vblank window or the reclock is taking too much time. I > wonder if it would make sense to wait for a vline rather than vblank, > say a vline 1/2 or 2/3 of the way down the screen, to give us some > buffer time between calling the reclock function and whatever setup it > does and the beginning of the actual vblank period.
If you suspect too slow resuming reclokcing context you can try tricks from: http://marc.info/?l=linux-kernel&m=126730151530139&w=2 It's about setting higher priority for reclocking context or switching to busy waiting. -- Rafał ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
