From owner-freebsd-current Fri May 15 03:11:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA22846 for freebsd-current-outgoing; Fri, 15 May 1998 03:11:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA22820; Fri, 15 May 1998 03:11:01 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id MAA02256; Fri, 15 May 1998 12:10:09 +0200 (CEST) To: Greg Lehey cc: dyson@FreeBSD.ORG, sos@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: People having problems with X windows? In-reply-to: Your message of "Fri, 15 May 1998 18:09:16 +0930." <19980515180916.J1953@freebie.lemis.com> Date: Fri, 15 May 1998 12:10:09 +0200 Message-ID: <2254.895227009@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19980515180916.J1953@freebie.lemis.com>, Greg Lehey writes: >> I just removed my WC "improvements", by adding the return to the >> subroutine in the pmap code. See if it is more friendly. The >> symptoms appear to be those associated with improper setting of >> WC mode for a display adaptor. I had to add a heuristic to make >> it work correctly on one of my cards, but I guess it was bad. >> >> The code is still in there, but I guess there is the need for more >> research into the issue. > >Excuse my ignorance, but what's WC in this context? Write Combining. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message