--- Michel D�nzer <[EMAIL PROTECTED]> wrote: > On Thu, 2004-02-26 at 15:37, Alex Deucher wrote: > > > > regarding the mouse problems, if you are using a fancy ARGB Xcursor > > theme, the cursor will be drawn with software. If so, that's > probably > > why the mouse flickers in blender. > > The radeon driver calls xf86ForceHWCursor() in TransitionTo3d() to > avoid > that.
We may have to do something similar with savage. I'll try and look into it at some point. > > > As far as xrandr goes, I'm not real familar with it and haven't > really > > used it much myself. I suspect it may need some driver hooks that > the > > savage driver just doesn't have. > > None that I'm aware of, for what that's worth. > > > I'm not really sure how xrandr plays with 3D in general since it > > adjusts the actual visual framebuffer size. > > AFAIK the actual framebuffer memory area is still static right now. > Actually I guess thinking about it more, the framebuffer would stay the same, just the announced dimensions would change and the viewport would be locked, so from the 2d/3d engine's perspecitive everything would be fine, there's just less "viewable" area. Alex > > -- > Earthling Michel Dänzer | Debian (powerpc), X and DRI > developer > Libre software enthusiast | > http://svcs.affero.net/rm.php?r=daenzer > __________________________________ Do you Yahoo!? Get better spam protection with Yahoo! Mail. http://antispam.yahoo.com/tools ------------------------------------------------------- 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
