Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!cbosgd!cwruecmp!shrimali
From: shrimali@cwruecmp.UUCP
Newsgroups: comp.unix.xenix
Subject: Xenix ver2.0 device-driver help
Message-ID: <2218@cwruecmp.UUCP>
Date: Mon, 10-Aug-87 00:10:09 EDT
Article-I.D.: cwruecmp.2218
Posted: Mon Aug 10 00:10:09 1987
Date-Received: Tue, 11-Aug-87 01:36:46 EDT
Sender: news@cwruecmp.UUCP
Organization: CWRU Dept. of Computer Engineering, Cleveland, OH
Lines: 13
Keywords: xenix device-driver


I would be grateful if somebody could provide some information
regarding writing a memory-mapped device driver for XENIX ver
2.0. I had successfully written one for version 1.0 which
apparently does not work well with 2.0. I have a call to
mmudesc() to have the segment descriptor corresponding to the
physical memory mapped as read/write data. I am suspecting this
as the culprit function as I have no documentation on it.
The rest of it looks kosher to me as it is in the same spirit of
the sample examples provided (this hasn't changed between versions).
Is there a way of choosing a global descriptor which can be used for this
purpose and not to conflict with other entries?
Thanks in anticipation.