Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!linus!decvax!wivax!cadmus!harvard!seismo!brl-tgr!internet!"Jonathan P. Leech" <jon@cit-vax.ARPA>
From: "Jonathan P. Leech" <jon@cit-vax.ARPA>
Newsgroups: net.unix-wizards
Subject: Mapping Kernel memory to user space
Message-ID: <5925@brl-tgr.ARPA>
Date: Tue, 20-Nov-84 03:23:21 EST
Article-I.D.: brl-tgr.5925
Posted: Tue Nov 20 03:23:21 1984
Date-Received: Wed, 21-Nov-84 05:19:16 EST
Sender: news@brl-tgr.ARPA
Organization: Ballistic Research Lab
Lines: 9


	We are running 4.2 on a 780. Recently our system manager implemented
a device driver which uses statically allocated RAM to emulate a frame buffer.
This works fine, but it would be nice to remove the overhead of system calls
on each read/write to the 'frame buffer'. Can anyone tell me how to make kernel
memory read and writeable from a normal process?
	Thanks,
	Jon Leech
	jon@cit-vax