The following significant changes have been made since 5.00
5.21 (This Release)
Official release of xDM 1.00. Examples and API Reference Guides
have been updated accordingly.
And the following MRs were resolved:
ID
Headline
SDSCM00014553
Remove dependency on BIOS types in idma3.h
SDSCM00013817
Deprecate XDM_ERUNTIME for xDM 1.00
SDSCM00013698
Add bitrate fields to several speech1 structs and more frame
types
SDSCM00013621
xDM 1.0 speech inArgs should have "size" field for extensibility
SDSCM00013568
xDM user guide needs to discuss extension of parameter ad
argument structions
SDSCM00013537
ISPHENC1_FrameType enums have inconsistant prefix
SDSCM00011273
When including public header files in xDAIS, one needs to
use "full qualified package path"
SDSCM00005724
xDAIS Documentation needs to be update to support IDMA3
5.10
Introduction of xDM 1.00 Beta.
The Reference Guide has been updated to include these Beta
APIs.
Added "What's New in xDM
1.00" documentation, describing the high-level changes in the
xDM 1.00 Beta specification.
This xDM 1.00 Beta spec addresses the following items:
SDSCM00004685 - xDM speech enc and dec OutArgs should
have extendedError field for consistency
SDSCM00005009 - IIMGDEC_OutArgs bytesconsumed should be
camelCase
SDSCM00005245 - Video enc interface needs to reconsider
reconBufs conventions for RPCs
Addition of example "copy" codecs, conforming with xDM 1.00 Beta
interfaces.
Addition of example G.711 algorithm, conforming with xDM 0.90
speech encoder interface. This example shows how to wrap an xDM
interface around an existing algorithm.
Addition of example "extended" video encoder copy codec. This
example shows how an algorithm can extend the xDM interface to
implement codec-specific features.
SDSCM00005726 - Add doxygen comments to ialg.h
SDSCM00005728 - IDMA3 channel object documentation needs to
include scratch environment support
SDSCM00010925 - xDM User's manual uses XMI in places
SDSCM00011274 - xDAIS header files for c55 need to include fully
qualified package files
ti.xdais - This package is compatible with the
previous release. (Compatibility key: 1,2.0,0,0 ->
1,2.0,0)
ti.xdais.dm - This package is compatible with
the previous release. A new interface (xDM 1.00) has been
added. (Compatibility key: 1,0,1,0 ->
1,0,2)
xDM 0.9 is equivalent to the xDM 0.9 interfaces provided
in xDAIS 5.10.
This is the first release of the final xDM 1.00
interfaces - xDAIS 5.10 included the beta xDM 1.00
interfaces, which are no longer supported.
The example codecs have been updated to meet the xDM 1.00
interface specification. Compatibility with previous releases
is not currently managed in the examples.
If migrating from a release prior to xDAIS 5.10, consult previous
releases available in the relnotes_archive directory.
Compatibility keys are intentionally independent of Marketing product
numbers are are intended to:
Enable tooling to identify incompatibilities between components,
and
Convey a level of compatibility between different releases to
set end user expectations.
Compatibility keys are composed of 3 comma-delimited numbers - M,S,R
- where:
M = Major. A difference in M indicates a break in
compatibility.
S = Source. A difference in S indicates source
compability, that is, the user's source doesn't require change, but
does require rebuilding.
R = Radix. A difference in R indicates an introduction
of new features, but compatibility with previous interfaces has not
broken. If libraries are provided by the package, an application
must re-link with the new libraries, but not rebuild from source.
This release was validated against using the following components:
The examples were built with the following versions of Code
Generation Tools. Note that, in general, nothing prevents them from
being built with a different version of tools, nor for other devices
- they are intentionally written in generic C):
This product's version follows a version format, M.mm.pp.bb,
where M is a single digit Major number, mm is 2 digit
minor number, pp is a 2 digit patch number, and b is an
unrestricted set of digits used as an incrementing build counter.
To support multiple side-by-side installations of the product, the
product version is encoded in the top level directory,
ex. xdais_5_21.
Subsequent releases of patch upgrades will be identified by the patch
number, ex. xDAIS 5.21.01 with directory dais_5_21_01. Typically,
these patches only include critical bug fixes.
