Path: utzoo!attcan!uunet!samsung!uakari.primate.wisc.edu!sdd.hp.com!hp-pcd!hpfcso!hpfcmgw!glen
From: glen@hpfcmgw.HP.COM (Glen Robinson)
Newsgroups: comp.sys.hp
Subject: Re: Needed: Interrupt handler.
Message-ID: <1080175@hpfcmgw.HP.COM>
Date: 28 Oct 90 23:15:41 GMT
References: <1628.2727168f@iccgcc.decnet.ab.com>
Organization: HP Fort Collins, CO
Lines: 41

kay@iccgcc.decnet.ab.com - writes:

>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
----------

Well, actually you've got a problem here.  VXI interrupts on the V/360 are
not the same class of critters as hardware vectored interrupts on VME.

Someone from the folks who support/market V360's correct me if I'm wrong
here but I believe that the VXI stuff gets put into a HP-UX interrupt
service request chain which is polled to determine the interrupt initiator.

VME on the other hand expects to vector directly to your driver's interrupt
routine.  You are probably going to have to write your own driver if you
need to handle hardware vectored interrupts.  The pertinent data is in
the HP-UX Driver Development Guide (98577-90011) for VME.  However, there
is nothing in there for the V360.  My guess is you would need to do the
appropriate mapping using the VXI driver to enable processor -- VME card
communication and then use your driver to handle the actual reads/writes/
interrupts et. al.  None of the above is trivial or for the faint of heart.

Finally, of course, make sure that your VME card does not use P2A or P2C
because VXI specifically defines these pins.

Best regards and good luck.

Glen R

The usual proclamations here that these comments are mine alone and do not 
reflect ... nor set policy ... for my employer.