[comp.sys.sgi] Reading/Writing VME bus

paulc@boulder.colorado.edu (Paul Connally) (02/15/91)

	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

olson@anchor.esd.sgi.com (Dave Olson) (02/15/91)

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.

paulc@boulder.colorado.edu (Paul Connally) (02/19/91)

Many thanks to all those who responded to my problem of talking to the VME
bus, everyone was a great help!

Especially Scott Townsend @ NASA Lewis Research Center and 
Archer Sully @ SGI for actual code.

Anyone interested in the replies should e-mail me and I'll send a copy
to them.

	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

marks@AIVAX.RADC.AF.MIL (David Marks) (02/20/91)

Paul,
  Yes, we are interested in the VME bus interface info you have received.
Please forward a copy.   Thanks!

Dave Marks
marks@aivax.radc.af.mil
Rome Laboratory