Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!julius.cs.uiuc.edu!wuarchive!usc!sdd.hp.com!hp-pcd!hpfcso!hplisa!hplvli!ronh
From: ronh@hplvli.HP.COM (Ron Hanson)
Newsgroups: comp.sys.hp
Subject: Re: Needed: Interrupt handler.
Message-ID: <26630003@hplvli.HP.COM>
Date: 7 Nov 90 00:04:50 GMT
References: <1628.2727168f@iccgcc.decnet.ab.com>
Organization: Loveland Inst. Div
Lines: 37

/ hplvli:comp.sys.hp / ronh@hplvli.HP.COM (Ron Hanson) /  4:50 pm  Nov  6, 1990 /
/ hplvli:comp.sys.hp / kay@iccgcc.decnet.ab.com /  3:45 pm  Oct 25, 1990 /

We're running HPUX 7.0 on a V/360 VXI workstation.  We've installed a VME
card in the VXI rack.  Can anyone tell us, or better yet, give us some example
code, on how to establish an interrupt handler for the VME card?

We have the VXI drivers software but the interrupt support doesn't seem to
apply to VME devices.

Thanks in advance.


Jim Kay
kay@astro.pc.ab.com
----------
----------

===============================================

I would like to add to all the previous responses the following notes:

The V/360 responds with a D32 IACK cycle in response to VME interrupts 
on the backplane.  It the device is a D32 interrupter, you will get all 
32 bits.  If the device is a D16 or D08(O) interrupter, then only the
lower 16 or 8 bits of the IACK word will be significant (the remaining
bits will be set to 1).  This allows the V/360 to handle the different
types of interrupters [as a matter of fact, the register-based device
examples in Larry Corsa's note are D16 interrupters].

Secondly, if you have multiple interrupters, remember to re-enable the
interrupt on the interface using the io_interrupt_ctl function in your
hanler.

Ron Hanson
Application Support Engineer
Loveland Instrument Division, Hewlett-Packard Company