From b18478077a7011418bf15a422bcda421b885b32a Mon Sep 17 00:00:00 2001 From: Andrew Johnson Date: Fri, 19 Oct 2018 14:44:52 -0500 Subject: [PATCH] Correct mbbi/oDirect release note entry Better wording from Dirk. Fixes LP: #1777985 --- documentation/RELEASE_NOTES.html | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/documentation/RELEASE_NOTES.html b/documentation/RELEASE_NOTES.html index 9d028f209..e0eb7ef39 100644 --- a/documentation/RELEASE_NOTES.html +++ b/documentation/RELEASE_NOTES.html @@ -66,15 +66,18 @@ release also includes additional protection against buffer overflows while printing long links in dbpr, and corrects the output of long strings from the dbgf command.

-

Record types mbbiDirect and mbboDirect extended to 32 bit

+

Record types mbbiDirect and mbboDirect upgraded to 32 bit

-

The VAL fields of mbbiDirect and mbboDirect records have -been extended from DBF_USHORT (16 bit) to DBF_LONG (32 bit). -New bit fields B10...B1F have been added.

+

The VAL fields and related fields of these records are now DBF_LONG. +(Not DBF_ULONG in order to prevent Channel Access from promoting them +to DBF_DOUBLE.) Additional bit fields B10...B1F have +been added.

-

Device support which accesses the bit fields can test if the macro -mbbiDirectRecord1BF or mbboDirectRecord1BF is -defined. Device support which only accesses RVAL needs no modification.

+

Device support that accesses VAL or the bit fields directly (most +don't) and aims for compatibility with old and new versions of these records +should use at least 32 bit integer types to avoid bit loss. The number of bit +fields can be calculated using 8 * sizeof(prec->val) +which is correct in both versions.

Restore use of ledlib for VxWorks command editing