Date: Tue, 03 Jul 2007 14:27:35 -0700 From: vehemens <vehemens@verizon.net> To: Adam K Kirchhoff <adamk@voicenet.com> Cc: freebsd-x11@freebsd.org Subject: Re: BERYL Response Times Message-ID: <200707031427.35842.vehemens@verizon.net> In-Reply-To: <1183451204.9886.4.camel@sorrow> References: <200707021802.28460.vehemens@verizon.net> <1183451204.9886.4.camel@sorrow>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 03 July 2007 01:26:44 am Adam K Kirchhoff wrote: > On Mon, 2007-07-02 at 18:02 -0700, vehemens wrote: > > I seeing BERYL window moves and cube rotation hesitation as much as > > several seconds after running for several minutes. Also after running > > for 30 minutes or so, I see a significant increase in response delays. > > > > I've read that BERYL has some problems, but none mention this type of > > runtime problem. > > > > The system is somewhat low end (XP 2100, 512MB, RADEON RV250), but it > > doesn't appear to be a resource problem. > > > > Is anyone else seeing this? If not, what's your configuration? > > _______________________________________________ > > Unless you applied some patches floating around this mailing list, the > radeon driver does not currently support AIGLX, which means that you are > using the copy render path. This is *much* slower than the normal > texture_from_pixmap render path. The one time I tried this, beryl > performed exactly as you described. I'm running xorg current with a patched DRM for an AIGLX initialization locking problem. I'm able to select texture_from_pixmap in the BERYL menu. Not sure what's being handled by GLX versus the driver.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200707031427.35842.vehemens>