W dniu 18 grudnia 2009 01:08 użytkownik Alex Deucher <alexdeuc...@gmail.com> napisał: > 2009/12/17 Rafał Miłecki <zaj...@gmail.com>: >> W dniu 17 grudnia 2009 06:43 użytkownik Alex Deucher >> <alexdeuc...@gmail.com> napisał: >>> 2009/12/16 Rafał Miłecki <zaj...@gmail.com>: >>>> V2: reorganize functions, fix modesetting calls >>>> V3: rebase patch, use radeon's workqueue >>>> V4: enable on tested chipsets only, request VBLANK IRQs >>>> V5: enable PM on older hardware (IRQs, mode_fixup, dpms) >>>> V6: use separate dynpm module parameter >>>> >>>> Tested on my M82==RV620 and my new M96==RV730. Also tested on RV515 by >>>> Sedat where already posted patch for AtomBIOS's mutex was needed. >>> >>> How does re-clocking happen if no crtcs are active? We will want to >>> be much more aggressive when the displays are off. >> >> Currently we treat such situation as 1 crtc active. That is something >> I want to improve in next patch when this one will be commitet. I hope >> it is not stopping issue. >> > > The issue you won't get vblank interrupts if the crtcs are off, so no > reclocking will occur.
Whoops, nice catch! -- Rafał ------------------------------------------------------------------------------ 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
