Path: utzoo!censor!comspec!lethe!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!helios!bcm!dimacs.rutgers.edu!seismo!ukma!wuarchive!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!sgi!shinobu!odin!anchor!olson
From: olson@anchor.esd.sgi.com (Dave Olson)
Newsgroups: comp.sys.sgi
Subject: Re: Reading/Writing VME bus
Message-ID: <1991Feb15.004508.27028@odin.corp.sgi.com>
Date: 15 Feb 91 00:45:08 GMT
References: <1991Feb14.171321.11620@csn.org>
Sender: news@odin.corp.sgi.com (Net News)
Organization: Silicon Graphics, Inc.  Mountain View, CA
Lines: 42

In <1991Feb14.171321.11620@csn.org> paulc@boulder.colorado.edu (Paul Connally) writes:


| 
| 	We currently have a PI (4D20) with Imaging Technologies IT-150
| video processsing boards connected to the VME bus.  I use some third
| party software to access these boards but it is not enough.
|  
| 	My question is this -
| 	How does one go about writing to the VME bus (in a C program)
| to access the registers on these boards? 
| 
| 	 I have all the docs for the boards and I know what addresses 
| they occupy but I'm really not sure how to get to them and I don't 
| want to go mucking about the bus without knowing exactly what I'm doing.
| 
| 	Also, do I have to deal with interrupts?  The boards can be
| configured to issue interrupts or not, the interrupt line (1-7), and the
| interrupt vector address.
| 
| 	Any hints, advice, or constructive comments is greatly appreciated.
| 
| 	Paul Connally          			University of Colorado
| 	Chief of Operations  			MCDB  -  Box 347
| 	High Voltage Electron Microscope Lab	Boulder, CO  80309
| 						paulc@boulder.colorado.edu
| 
| 	
| 	Paul Connally          			University of Colorado
| 	Chief of Operations  			MCDB  -  Box 347
| 	High Voltage Electron Microscope Lab	Boulder, CO  80309
| 						paulc@boulder.colorado.edu

Ask your SGI sales office for this document:

SGI Document #: 007-0911-010
Writing Device Drivers for Silicon Graphics Computer Systems
--

	Dave Olson

Life would be so much easier if we could just look at the source code.