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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Proposed change in asyn interruptCallback APIs |
From: | Andrew Johnson <[email protected]> |
To: | Mark Rivers <[email protected]> |
Cc: | Eric Norum <[email protected]>, tech-talk tech-talk <[email protected]> |
Date: | Thu, 29 Mar 2007 14:00:50 -0500 |
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.
- Andrew -- The right to be heard does not automatically include the right to be taken seriously. -- Hubert H. Humphrey