On May 30, 2012, at 6:53 PM, Kim, Kukhee wrote:
> Hi Mark;
>
> I just read this mail thread.
>
>> - asyn device support sets the record timestamps based on pasynUser->timeStamp if the following are both true:
>> - The record TSE field is set to epicsTimeEventDeviceTime (-2)
>> - pasynUser->timeStamp is non-zero
Actually the asyn devEpics layer is simpler than described above.
- It always sets the record TIME field from the pasynUser->timestamp in the device support interrupt callback or read method then returns to higher level record processing code.
- The record processing code then overwrites the TIME field unless the TSE field is -2.
I've sent a patch file with some proof-of-concept changes. Hopefully Mark will have time to check them and commit the changes to the subversion repository some time next week.
--
Eric Norum
[email protected]
- Replies:
- Re: Proposed change in asyn - request for comments Andrew Johnson
- References:
- Proposed change in asyn - request for comments Mark Rivers
- Re: Proposed change in asyn - request for comments Ernest L. Williams Jr.
- Re: Proposed change in asyn - request for comments Eric Norum
- RE: Proposed change in asyn - request for comments Mark Rivers
- Re: Proposed change in asyn - request for comments Bruce Hill
- RE: Proposed change in asyn - request for comments Kim, Kukhee
- Navigate by Date:
- Prev:
errro running "ibtest" tzk6s
- Next:
Re: [CSS] commas in TextUpdate Pavel Masloff
- 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: Proposed change in asyn - request for comments Kim, Kukhee
- Next:
Re: Proposed change in asyn - request for comments Andrew Johnson
- 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
|