2009/12/26 Rafał Miłecki <zaj...@gmail.com>: > W dniu 26 grudnia 2009 02:46 użytkownik Rafał Miłecki > <zaj...@gmail.com> napisał: >> There are some my experiments with engine. Reclocking between: >> 1) 110MHz and 680MHz - 1 corrupted frame on every reclock >> 2) 200MHz and 680MHz - 1 corrupted frame on almost every reclock >> 3) 250MHz and 680MHz - no corruptions >> 4) 340MHz and 680MHz - no corruptions >> 5) 630MHz and 680MHz - no corruptions > > Done more testing. Reclocking between: > 1) 110MHz and 250MHz - 1 corrupted frame on every reclock > 2) 110MHz and 130MHz - 1 corrupted frame on every reclock > > I don't have more ideas :|
It may be that the engine doesn't like to be reclocked while it's running. Perhaps we should use the GUI idle interrupt rather than vblanks to reclock the engine. Alex ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
