epics/epics-base
0
0
Fork 0
Code Issues Pull Requests Projects Wiki Activity

more changes for dbCaPutCallback

Browse Source
This commit is contained in:
Marty Kraimer
2003-12-16 20:13:36 +00:00
parent fff249dd3a
commit 258ebe6bcd
1 changed files with 14 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
documentation/RELEASE_NOTES.html
View File

@@ -48,16 +48,25 @@ the above bug the delay was more like 64 mS. </p>
<h4>dbCa</h4>
<p>Better error messages are now generated.</p>
<p>dbCaPutLinkCallback is a new function. It provides the ability to implement record/driver
support that does not complete until a channel access put callback has completed. See the Application Developer's Guide for details.</p>
<p>dbCaPutLinkCallback is a new function.
It provides the ability to implement record/driver
support that does not complete until a channel access put callback
has completed. See the Application Developer's Guide for details.</p>
<p>dbCaAddLinkCallback is a new function.
The caller can provide a connect and monitor callback.
See the Application Developer's Guide for details.</p>
<h4>devXxSoftCallback</h4>
<p>Soft device that uses dbCaPutLinkCallback has been written for
ao, bo, longout, mbbo, mbboDirect, and stringout records. To use these
your xxxInclude.dbd must have:</p>
<pre> include "devSoftCallback.dbd"</pre>
ao, bo, calcout, longout, mbbo, mbboDirect, and stringout records.
The dbd definitions have been added to devSoft.dbd.
In other to use the new support the DTYP field is defined:</p>
<pre> field(DTYP,"Async Soft Channel")</pre>
<h4>calcoutRecord</h4>
<p>The CALC and OCAL fields now have a size of 40 so that they are the
same as the calcRecord.</p>
<p>calcoutRecord now has associated device support. The default support
will act just like the old calcout. Support bis also available that uses
dbCaPutLinkCallback.</p>
<h4>mbbiRecord</h4>
<p>The fields ZRST,...,FFST are now special(SPC_MOD).</p>
<h4>mbboRecord</h4>