IMGLIB 3.1.1.0 Release Notes

May 29, 2012

IMGLIB Bundle Release Notes

Contents

  1. Introduction
  2. Getting Started
  3. Documentation
  4. What's New
  5. Upgrade and Compatibility Information
  6. Device Support
  7. Validation Information
  8. Known Issues
  9. Technical Support
  10. Component Release Notes

Introduction

The IMGLIB bundle comprises the Image and Video Processing Library package together with the software tools (SWTOOLS) package in bundle format to simplify the release procedure.

Getting Started

The IMGLIB User's Manual provides the documentation and references necessary to integrate IMGLIB Library routines into a development platform.

Documentation

The following documentation is available:

User's Manual [HTML]
[CHM]
Test Report [HTML]
Software Manifest [HTML]
Release Notes Archive [LINK]

What's New

The following new features were added:

  1. Added CCS 5.1 support for building the library

The following bugs have been resolved:

  1. IR #92280: IMGLIB Release 3.1.0 missing kernels in c66x libraries
  2. IR #92362: IMGLIB build project doesn't work in CCS 5.1
  3. IR #91885: IMGLIB compiler warnings
  4. IR #88808: Release notes should not direct user to local FAE

Upgrade and Compatibility Information

This version of IMGLIB is compatible with the last released version:

YES X
NO

Note:
  1. Package compatibility keys are independent of component release versions. For more information visit: Package Versioning and Compatibility

Device Support

This release supports the following device families:

Validation Information

This release was built and validated using the following tools:

Known Issues

  1. N/A

Technical Support

Questions regarding the IMGLIB library should be directed to the Texas Instruments BIOS E2E Forum. Please include the text "IMGLIB" in the title and add "C66x" and "IMGLIB" tags to your post.

Component Release Notes

  1. IMGLIB Release Notes

Package Versioning and Compatibility

Compatibility Keys

Compatibility keys serve two primary purposes:

  1. Enable tooling to identify incompatibilities between components
  2. Convey a level of compatibility between different releases to set end user expectations.

Each compatibility key is composed of 4 comma-delimited numbers - represented here by the letters M, S, R and P [M,S,R,P]. The table below provides a descriptive reference for compatibility key intention.

Compatibility Key Reference
Key Meaning Description
1 (M=Major) Break in compatibility The package consumer is required to re-write the calling source code to use the package
2 (S=Source) Source compatibility The package consumer’s source code doesn't require change, but does require a recompile
3 (R=Radix) Introduction of new features 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
4 (P=Patch) Bug fixes only If libraries are provided by the package, an application must re-link with the new libraries, but is not required to recompile its source.

Versioning

Each package version is composed of 4 period-delimited numbers - represented here by the letters M, m, p and b [M.m.p.b]. The table below provides a descriptive reference regarding package version numbering.

Package Version Reference
Digit Meaning Description
1 (M=Major) Major revision Incremented when the new version is substantially different from the previous For example, a new module added or an existing module's algorithm significantly altered.
2 (m=minor) Minor revision Incremented when the new version has changed but not in a major way. For example, some minor changes in the API or feature set.
3 (p=patch) Patch number Incremented for all other source code changes. This include any packaging support code.
4 (b=build) Build number Incremented for each release delivery to CM. Reset for any change to M, m or p

Copyright 2012, Texas Instruments Incorporated