RFCS 4.0.1.0 Release Notes
May 10, 2011
Introduction, Documentation, What's New Upgrade and Compatibility Information, Host Support, Device Support, Validation Information, Known Issues, Version Information, Technical Support
Introduction
IETF Request for Comments (RFCS) for every codec specifies a) mapping the bit stream onto RTP packets b) specifications for the use of RTP header fields c) fragmentation rules d) specifications for Multipurpose Internet Mail Extensions (MIME) type registrations e) use of Session Description Protocol (SDP)
VPPU encapsulates all the RFCs in Video GDK
back to top
Documentation
The following documentation is available:
Release notes from previous releases are also available in the relnotes_archive directory.
back to top
What's New
The following new features were added:
back to top
Upgrade and Compatibility Information
This ti.mas.rfcs version is compatible with the last released ti.mas.rfcs version.
Please note that the package compatibility keys are independent of XDC product release numbers.
Package compatibility keys are intended to:
- Enable tooling to identify incompatibilities between components, and
- Convey a level of compatibility between different releases to set end user expectations.
Package compatibility keys are composed of 4 comma-delimited numbers - M, S, R, P - where:
- M = Major - A difference in M indicates a break in compatibility. The package consumer is required to re-write its source code in order to use the package.
- S = Source - A difference in S indicates source compatibility. The package consumer’s source code doesn't require change, but does require a recompile.
- R = Radix - A difference in R indicates an introduction of new features, but compatibility with previous interfaces is not broken. If libraries are provided by the package, an application must re-link with the new libraries, but is not required to recompile its source.
- P = Patch - A difference in P indicates that only bugs have been fixed in the latest package and no new features have been introduced. If libraries are provided by the package, an application must re-link with the new libraries, but is not required to recompile its source.
back to top
Host Support
The current XDC toolset can be used to build components on the following hosts:
back to top
Device Support
back to top
Validation Information
This release was built and validated using the following components:
Component Dependencies
- ti.mas.types 5.5.3.0 (Common data type definitions)
- ti.mas.swtools 4.6.0.12 (Internally used s/w tools)
- ti.mas.util 4.7.3.0 (Common utilities)
- ti.mas.iface.ifrfc 4.0.0.0 (RFC interface)
- ti.mas.iface.ifvisys 2.0.0.0 (Video GDK System Interface)
Tool Dependencies for Source Release
- XDC Tools version 3.20.5.76
- RTSC Packaging Standard version 1.00.00
- C6x Code Generation Tools version 7.2.02
back to top
Known Issues
None.
back to top
Versioning
This product's version follows a version format, M.m.x.p, where M is a single digit Major number, m is single digit minor number, x is single digit vertical numbner and p is a single digit patch number
Please note that version numbers and compatibility keys are NOT the same. For an explanation of compatibility keys, please refer to the 'Upgrade and Compatibility Information' section.
back to top
Technical Support
Contact local TI Field Application Engineer for technical support.
back to top
Copyright 2011, Texas Instruments Incorporated