From owner-freebsd-hackers Mon Oct 27 23:40:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA04118 for hackers-outgoing; Mon, 27 Oct 1997 23:40:40 -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 XAA04108 for ; Mon, 27 Oct 1997 23:40:33 -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 SAA01858; Tue, 28 Oct 1997 18:06:24 +1030 (CST) Message-Id: <199710280736.SAA01858@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Christoph Kukulies cc: Mike Smith , Peter Dufault , freebsd-hackers@freefall.FreeBSD.org Subject: Re: mmap/mlock problem In-reply-to: Your message of "Tue, 28 Oct 1997 08:27:05 BST." <19971028082704.21011@gil.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Oct 1997 18:06:24 +1030 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > The portion of code behaves correctly when executed in the > driver but executed in the user process (being root) it behaves > differently. (accessing the memory region mapped by the driver). Ah, now I understand. I think you said this before. Can you show us how you are mapping, and then accessing the device? It sounds like you've got something confused in either the driver or the application, as the memory region itself is OK. mike