🚀 go-pugleaf

In article <1i8votINN2ro@sgi.iunet.it> peanuts@dist.dist.unige.it (Baudino Alberto Bruzzone Gabriele Durante Antonio) writes:
> we need informations
> about VMEXEC and interrupts on VME BUS
> (e.g. how generate an interrupt from C language, 
> how catch the interrupt, ...).

I am passing on the following from Mike Duh, duh@phx.mcd.mot.com.
Please contact him by email if you have further questions.

VMEexec  easily  supports  handling  interrupts   from   "C"
language.   Under  VMEexec, you would create a src/task (for
non-SVIDlib tasks) or src/ctask (for  SVIDlib  tasks).   The
task  issues the claimvct System Service call which connects
an interrupt to a routine contained in the  task.   Assuming
VMEexec 2.0 or later is used, documentation for tasks can be
found in chapter 3 of the VMEexec  User's  Guide  (ADDING  A
TASK).   The  claimvct  service is documented in the VMEexec
System Services User's Manual.

Your specific application requested information on  handling
VMEbus interrupts on the MVME167 so there is some additional
code which must be written.  All of  the  VMEbus  interrupts
are handled by the VMEchip2 on the MVME167.  The VMEchip2 is
initialized     by     VMEexec      in      the      module:
src/board/68040/vme167/mvme167.c.   It  is  likely  that the
specific interrupt needed for your application  is  disabled
by  default.  However, since the source for the above module
is  supplied  with  VMEexec,  this  default  action  may  be
changed.   Refer  to  the MVME167/187 Programmer's Reference
Manual  to  locate  the  specific  VMEchip2  register  which
controls  the  interrupt  needed for your application.  Then
edit the default VMEchip2 initialization code  in  mvme167.c
to  enable  the  interrupt  and program it to interrupt on a
level and vector  of  your  choice.   The  vector  must  not
overlap with any other vectors already used.