Mark Rivers wrote:
I have found a problem in the APIs used by device support to receive
callbacks from asynDrivers. These are the callbacks that an asyn driver
supports via pasynManager->registerInterruptSource, and device support
accesses via, for example, pasynInt32->registerInterruptUser. These
callbacks allow EPICS records to have "I/O Intr" record processing, i.e.
the record only gets processed when the driver calls back device support
with "new" data.
Assuming that the only changes you'd be making to the asyn API would be
to the routines mentioned, i.e. pasynManager->registerInterruptSource()
and to methods for specific ASYN message types such as asynInt32 (but
not to asynOctet) then this should not affect my directNetAsyn layer at all.
If you make any non-trivial changes to asynOctet I'm sure mine would not
be the only code affected, but from your description it doesn't appear
that this will be necessary.
- Andrew
--
The right to be heard does not automatically include
the right to be taken seriously. -- Hubert H. Humphrey
- References:
- Proposed change in asyn interruptCallback APIs Mark Rivers
- Navigate by Date:
- Prev:
Re: .cmd file downloading problem Kate Feng
- Next:
Re: Maximum archival rate Maren Purves
- 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:
Proposed change in asyn interruptCallback APIs Mark Rivers
- Next:
Obituary for Coles SIbley who worked with our community at MIT Bates and Oak Ridge National Lab Dalesio, Leo `Bob`
- 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
|