From owner-freebsd-alpha Thu Jul 20 12:19: 1 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D05A937BE90 for ; Thu, 20 Jul 2000 12:18:59 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA09402; Thu, 20 Jul 2000 12:18:57 -0700 Date: Thu, 20 Jul 2000 12:19:00 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: freebsd-alpha@freebsd.org Subject: Re: fxp0 hangs on a PC164 using STABLE In-Reply-To: <200007201911.PAA15726@gale.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 20 Jul 2000, Andrew Gallatin wrote: > On the last, (putting in a memory barrier) -- I object because its implicit > in the atomic instructions & would be totally superfulous. An addition > to the comment to point this out might be appropriate though.. Okay. > WRT memory barriers on i86 -- I though that writes to device memory space > were uncachable & flushed the write buffers unless an mtrr was set > up for the region & it was made cacheable. I defer to the i86 experts.. Which could happen. > As for flushing writes to main memory for better device communication, > I have no clue.. > > Drew > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message