From owner-freebsd-hackers Sat Apr 11 13:24:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01092 for freebsd-hackers-outgoing; Sat, 11 Apr 1998 13:24:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ece.WPI.EDU (root@ece.WPI.EDU [130.215.16.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA01086 for ; Sat, 11 Apr 1998 13:24:28 -0700 (PDT) (envelope-from bad@ece.WPI.EDU) Received: from taz.WPI.EDU (bad@taz.WPI.EDU [130.215.16.19]) by ece.WPI.EDU (8.8.5/8.6) with ESMTP id QAA27621; Sat, 11 Apr 1998 16:23:23 -0400 (EDT) Received: from localhost (bad@localhost) by taz.WPI.EDU (8.8.5/8.6) with SMTP id QAA20129; Sat, 11 Apr 1998 16:22:36 -0400 (EDT) X-Authentication-Warning: taz.WPI.EDU: bad owned process doing -bs Date: Sat, 11 Apr 1998 16:22:36 -0400 (EDT) From: Bernie Doehner To: hackers@FreeBSD.ORG Subject: Documentation of 2.2.5-RELEASE and 3.0 memory protection? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi: Is there a document that describes the kernel memory protection/allocation scheme used in 2.2.5-RELEASE and 3.0? I am especially interested in a list of io-space and io-memory ranges which I am allowed to read/write from in user space without worrying about interfering/overlapping into the kernel's memory space. Thanks.. Bernie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message