From owner-freebsd-x11@FreeBSD.ORG Tue Jul 3 21:27:45 2007 Return-Path: X-Original-To: freebsd-x11@freebsd.org Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 81C7416A400 for ; Tue, 3 Jul 2007 21:27:45 +0000 (UTC) (envelope-from vehemens@verizon.net) Received: from vms042pub.verizon.net (vms042pub.verizon.net [206.46.252.42]) by mx1.freebsd.org (Postfix) with ESMTP id 6542C13C4C5 for ; Tue, 3 Jul 2007 21:27:45 +0000 (UTC) (envelope-from vehemens@verizon.net) Received: from susy.dsl-verizon.net ([71.107.39.21]) by vms042.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0JKM00BB9GY27LR9@vms042.mailsrvcs.net> for freebsd-x11@freebsd.org; Tue, 03 Jul 2007 16:27:38 -0500 (CDT) Date: Tue, 03 Jul 2007 14:27:35 -0700 From: vehemens In-reply-to: <1183451204.9886.4.camel@sorrow> To: Adam K Kirchhoff Message-id: <200707031427.35842.vehemens@verizon.net> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline References: <200707021802.28460.vehemens@verizon.net> <1183451204.9886.4.camel@sorrow> User-Agent: KMail/1.9.6 Cc: freebsd-x11@freebsd.org Subject: Re: BERYL Response Times X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jul 2007 21:27:45 -0000 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.