From owner-freebsd-ports Thu Aug 15 7:33:33 2002 Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 433C337B406; Thu, 15 Aug 2002 07:33:28 -0700 (PDT) Received: from smtp3.southeast.rr.com (smtp3.southeast.rr.com [24.93.67.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F44643E72; Thu, 15 Aug 2002 07:33:27 -0700 (PDT) (envelope-from bts@fake.com) Received: from mail4.nc.rr.com (fe4 [24.93.67.51]) by smtp3.southeast.rr.com (8.12.5/8.12.2) with ESMTP id g7FEXAgc018889; Thu, 15 Aug 2002 10:33:12 -0400 (EDT) Received: from this.is.fake.com ([66.26.254.93]) by mail4.nc.rr.com with Microsoft SMTPSVC(5.5.1877.757.75); Thu, 15 Aug 2002 10:33:25 -0400 Received: by this.is.fake.com (Postfix, from userid 111) id BF1EABB34; Thu, 15 Aug 2002 10:33:01 -0400 (EDT) Content-Type: text/plain; charset="iso-8859-1" From: "Brian T. Schellenberger" To: Alan E Subject: Re: xv patch for refresh problem Date: Thu, 15 Aug 2002 10:33:01 -0400 User-Agent: KMail/1.4.2 Cc: freebsd-ports@freebsd.org, shige@freebsd.org References: <200208150932.34230.bts@babbleon.org> <20020815141715.GA8569@wwweasel.geeksrus.net> In-Reply-To: <20020815141715.GA8569@wwweasel.geeksrus.net> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200208151033.01266.bts@babbleon.org> Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thursday 15 August 2002 10:17 am, Alan E wrote: | On Thu, Aug 15, 2002 at 09:32:34AM -0400, Brian T. Schellenberger wrote: | >[ooops . . . Hit send too soon. Forgot the primary recipient. Sorta | >important.] | > | > | >There is a bug in xv 3.10a that causes it not to refresh properly with | > recent releases of XFree86 and FreeBSD. (Eg, it started getting really | > bad when I upgraded to FreeBSD 4.6 and XFree86 4.2.) | | There's a command line option that fixes it, too. Do we need to do | anything but force that on? | | The option is "-loadclear". Wowsers. I wish somebody had mentioned that before. I'd sent mail to about a half-dozen groups (but not this one, I guess) at earlier stages while I was trying to figure this out. Of course, I started out believing it to be a bug in the X server or something since those had changed and xv had not. Even my first-pass xv patch I submitted to the X groups not to here because I was asking why this kludge (a nanowait for one nonosecond in my first version) fixed it rather than thinking it was truly an xv bug. Nonetheless, my opinion, now that I have a working patch, is that it's silly to have to specify an option just to get basic functionality to work, and it would be better to go ahead and apply the patch. Not to mention the fact that it's a total kludge that "loadclear" even *works*. It's meant to solve problems with psuedocolor displays, which I am not using. So rather than being a fix it's more like a coincidence--the equivalent of my preliminary "nanowait" patch rather than a real fix like the current patch. The FreeBSD port of xv already has a large number of patches, so it's not as if we would be messing up the pristine state of the shipped xv by doing this, nor is it as if there's any realistic hope that the "real" xv will get the fix anytime soon. -- Brian, the man from Babble-On . . . . bts@babbleon.org (personal) http://www.babbleon.org http://www.eff.org http://www.programming-freedom.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message