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).
- Replies:
- RE: Interrupts Jeff Hill
- References:
- PID records Benjamin Franksen
- Re: PID records Marty Kraimer
- Re: PID records Jim Thomas
- Re: PID records Marty Kraimer
- Navigate by Date:
- Prev:
Re: PID records Marty Kraimer
- Next:
RE: Interrupts Jeff Hill
- Index:
1994
1995
1996
1997
1998
1999
<2000>
2001
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:
Re: PID records Marty Kraimer
- Next:
RE: Interrupts Jeff Hill
- Index:
1994
1995
1996
1997
1998
1999
<2000>
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|