Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!uwm.edu!uakari.primate.wisc.edu!ginosko!usc!henry.jpl.nasa.gov!elroy.jpl.nasa.gov!ucla-cs!uci-ics!zardoz!tgate!ka3ovk!drilex!axiom!linus!chance!dougw From: dougw@chance.uucp (Doug Worthington) Newsgroups: comp.unix.xenix Subject: Device Drivers for Xenix and Imaging Technology digitizers Message-ID: <71079@linus.UUCP> Date: 13 Sep 89 19:52:38 GMT Sender: news@linus.UUCP Reply-To: dougw@chance.UUCP (Doug Worthington) Organization: MITRE-McLean Software Engineering Laboratory Lines: 16 I have a two part problem dealing with xenix 2.3.0 on a zenith 386 using an imaging technology PC Vision-Plus digitizing board. 1. Does anybody have a device driver to support this configuration 2. If anybody has experience writting device drivers for under xenix this is small description of my problem. I have a device driver to interact with the digitizer that was written for 2.2.x and utilizes calls to dscralloc and mmudescr. These calls are not appropriate under 2.3.0 on a 386 machine. In order to map memory for use by the device I think I should use mapptov or mapphys. I realize mapptov should only be called in the initialization routine but I don't know the difference between these two calls because they both describe the same capability. If anybody can help I would appreciate it. doug wortington Internet : dougw@community-chest.mitre.org