From owner-freebsd-hackers Mon Oct 27 18:13:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA15999 for hackers-outgoing; Mon, 27 Oct 1997 18:13:34 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA15993 for ; Mon, 27 Oct 1997 18:13:29 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost.gsoft.com.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id MAA00972; Tue, 28 Oct 1997 12:39:29 +1030 (CST) Message-Id: <199710280209.MAA00972@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Christoph Kukulies cc: Peter Dufault , freebsd-hackers@freefall.FreeBSD.org Subject: Re: mmap/mlock problem In-reply-to: Your message of "Mon, 27 Oct 1997 15:11:39 BST." <19971027151139.61831@gil.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Oct 1997 12:39:29 +1030 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [memory-mapped peripheral's space appears to be cached] > There is a 80186 on the board which communicates > over some semaphores in the memory region with the outside world. > You write a command into the location and that location must read > as 0000 or FFFF if the board is ready or not resp.. Actually it's quite > weird - I have the source of a DOS program which communicates with > the board. (This is written for Borlandc/16 bit) Does the sample source attempt to invalidate the processor's cache for the region? Is it possible that your BIOS is set to consider the address range occupied by the card as cacheable? mike