Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!bionet!agate!ucbvax!tut.cis.ohio-state.edu!rutgers!att!alberta!ubc-cs!grads.cs.ubc.ca!acton From: acton@grads.cs.ubc.ca (Donald Acton) Newsgroups: comp.sys.apollo Subject: Help! busses + DN10000 Message-ID: <1824@ubc-cs.UUCP> Date: 19 Apr 89 15:42:55 GMT Sender: news@cs.ubc.ca Reply-To: acton@cs.ubc.ca (Donald Acton) Organization: UBC Department of Computer Science, Vancouver, B.C., Canada Lines: 34 We just recently got an Apollo DN10000 and are running with ENVIRONMENT set to bsd and SYSTYPE set to bsd4.3 under SR10.0.2. Coming from a Sun/UNIX environment I am still making my way through the various Apollo documents so pointers to the relevant places to help me solve the following problem would be greatly appreciated. We have two different boards we would like to install on the machine, one in the VMEbus and the other on the PC AT compatible bus. What I would like to do is map the bus address spaces for these boards into the application address space and let the application control the boards directly. (The interface to these boards is very simple. The VMEbus board also has dual ported RAM on it that we would like to map directly into then application's address space.) We are already doing this on our Sun with the VMEbus board through the use of the mmap(2) system call and I am hoping there is something similar for the Apollo. Upon checking out the documentation for mmap(2) on the Apollo it says that mmap cannot be used on device special files so it initially appears that I am out of luck in that department. My questions are: 1) Is there a simple way to do what I want in a vein similar to that provided by the mmap call? 2) If the answer to 1 is no then do I have to write a device driver and if so where should I look for advice? (I have written device drivers for other machines running UNIX so this won't be an entirely new experience for me.) Any help would be greatly appreciated. Thanks in advance. Donald Acton acton@cs.ubc.ca