From owner-freebsd-current Fri May 15 01:57:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA10900 for freebsd-current-outgoing; Fri, 15 May 1998 01:57:40 -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 BAA10887; Fri, 15 May 1998 01:57:35 -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 KAA02030; Fri, 15 May 1998 10:56:51 +0200 (CEST) To: dyson@FreeBSD.ORG cc: sos@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: People having problems with X windows? In-reply-to: Your message of "Fri, 15 May 1998 02:38:54 CDT." <199805150738.CAA03075@dyson.iquest.net> Date: Fri, 15 May 1998 10:56:50 +0200 Message-ID: <2028.895222610@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199805150738.CAA03075@dyson.iquest.net>, "John S. Dyson" 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. I would expect WC to break any and all accelerated adapters that communicate with the graphics engine through the ram window... What is needed is to XFree86 to be able to madvise the true frame buffer as "Write-combine" and leave the rest of the ram window unaffected. -- 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