EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  <20002001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  <20002001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: Interrupts
From: [email protected] (Jeff Hill)
To: "Dmitrovskiy Alexei" <[email protected]>, <[email protected]>
Date: Wed, 5 Jul 2000 10:02:45 -0600

There are files in base {devLib.h, devLib.c} which attempt
to isolate device drivers from operating system variations, and 
also attempts to detect conflicts where two different device drivers 
are configured to use the same hardware resources. This code
does attempt to detect when two device drivers are attaching
to the same interrupt vector. The vxWorks services are a bit weak in 
this area and so some small additional 68k architecture dependent 
support code was provided, but there is currently no support for this 
on Pentium/486/386 or on PPC architectures although I cant imagine
that it would be difficult for some site to make the necessary 
extensions.

This code has been mostly dormant for several years. It could
probably use more active management. We would certainly welcome
any assistance volunteered from persons interested in upgrading 
or extending it.

Jeff

> -----Original Message-----
> From: Dmitrovskiy Alexei [mailto:[email protected]]
> Sent: Tuesday, July 04, 2000 4:25 AM
> To: [email protected]
> Subject: Interrupts
> 
> 
> Hello,
> 
> Does anyone have an idea how to manage the allocation of interrupt vectors
> while working with IOCs?
> For IP modules it could be solved on the IPAC driver level, but what about
> other specific drivers (to rewrite?!.)...
> As I understand at the moment interrupt vectors are fixed for each device
> driver according to a programmer taste. Could this situation be improved?
> At DESY we have integrated an inhouse-made IOC hardware (GPFC) developed
> together with IHEP (Russia). Our new device drivers for IP modules are built
> around Andrew's IPAC driver.
> In case of the GPFC usage ipmIntConnect calls a function administrating
> interrupts vectors. Slight changes were necessary in the IPAC driver.
> What's about other platforms and more heterogeneous systems? How can an
> intelligent management of available vector numbers be achieved?
> 
> Let's make our life better! :)
> 
> Regards,
> Alexei (together with Bernd Schoeneburg).
> 


References:
Interrupts Dmitrovskiy Alexei

Navigate by Date:
Prev: Interrupts Dmitrovskiy Alexei
Next: Problems with the CA lib under LynxOS with R3.13.2 Benjamin Sailer
Index: 1994  1995  1996  1997  1998  1999  <20002001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Interrupts Dmitrovskiy Alexei
Next: RE: PID records Mark Rivers
Index: 1994  1995  1996  1997  1998  1999  <20002001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·