shrimali@cwruecmp.UUCP (08/10/87)
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.