From: Michel <mi...@da...> - 2002-10-12 12:57:26
|
On Sam, 2002-10-12 at 11:53, Giorgio Terzi wrote: > Alle 14:50, venerd=EC 11 ottobre 2002, Michel D=E4nzer ha scritto: >=20 > > > The warbled text problem i signaled succedes only in the X text windo= ws > > > as Xterm or Mozilla and so on. I think this is a driver's limitation > > > because with 1024x768x16 resolution this succedes only when the machi= ne > > > is very stressed but with 1152x864x16 and over this succedes everytim= e i > > > open a window. With these high resolutions it warbles also the graphi= cs. > > > > Sounds like bus contention and/or synchronization problems in the 2D > > acceleration code. >=20 > I think that what you are saying is also (or something near) the reason > why the framebuffer crashes after a vterm exchange from X . > Is it possible that X is not signalled to release its resources and go to= =20 > sleep ? It does, but one potential problem I see is that the glint driver still lets the driver independent code call fbdevHW functions directly. I've modified the radeon driver in DRI CVS to always go through driver functions and make sure the acceleration engine is idle before calling an fbdevHW function. You may want to take a look at that and try something similar with the glint driver. --=20 Earthling Michel D=E4nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast |