From owner-freebsd-current Fri May 15 07:49:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06156 for freebsd-current-outgoing; Fri, 15 May 1998 07:49:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com ([210.145.37.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06143; Fri, 15 May 1998 07:49:29 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id GAA00574; Fri, 15 May 1998 06:44:16 -0700 (PDT) Message-Id: <199805151344.GAA00574@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Poul-Henning Kamp 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 10:56:50 +0200." <2028.895222610@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 15 May 1998 06:44:15 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I would expect WC to break any and all accelerated adapters that > communicate with the graphics engine through the ram window... Why? If the region doesn't support bursting, it should disallow it in the PCI configuration registers. A combined write is (should be) flushed at the first read, so it won't break any synchronisation. (I'm not saying it doesn't, as there are obviously problems, I'm just curious why it might...) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message