From owner-freebsd-hackers Mon Oct 27 04:20:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA13780 for hackers-outgoing; Mon, 27 Oct 1997 04:20:33 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA13768 for ; Mon, 27 Oct 1997 04:20:28 -0800 (PST) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from gil.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by Campino.Informatik.RWTH-Aachen.DE (8.8.7/RBI-Z14) with ESMTP id NAA08255 for ; Mon, 27 Oct 1997 13:19:47 +0100 (MET) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.8.5/8.6.9) id NAA03303 for freebsd-hackers@freefall.cdrom.com; Mon, 27 Oct 1997 13:31:56 +0100 (MET) Date: Mon, 27 Oct 1997 13:31:56 +0100 (MET) From: Christoph Kukulies Message-Id: <199710271231.NAA03303@gil.physik.rwth-aachen.de> To: freebsd-hackers@freefall.FreeBSD.org Subject: mmap/mlock problem Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I've written a driver for an industrial control card (portions of it coppered from /sys/i386/isa/spigot.c as far as the mmap stuff is concerned) With regard to the mapping into a user program it seems to work but the mapped memory region behaves differently in the user process. The ISA mapped memory is a dual ported RAM which is controlled by the on board CPU on one end and the user process on the other end. Writing something into the ISA memory should not result in reading the same back from it. But the fact of the matter is that I read back what I'v written into it and this seems to me as if the memory is cached. I tried a mlock call on the mmapped region but this seems to fail in the user process. Can anyone give me some assistance on getting further here? -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de