[ep-processor-libraries/dsplib.git] / ti / dsplib / docs / dsplib / docs / relnotes_archive / dsplib_3_0_0_8_release_notes.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2 <html><head><meta http-equiv="Content-Type" content="text/html;charset=iso-8859-1">
3 <title>DSPLIB Bundle Release Notes</title>
4 <link href="doxygen.css" rel="stylesheet" type="text/css">
5 <link href="tabs.css" rel="stylesheet" type="text/css">
6 </head><body>
7 <table width=100%>
8 <tr>
9 <td bgcolor="black" width="1"><a href="http://www.ti.com"><img border=0 src="docs/relnotes_archive/tilogo.gif"></a></td>
10 <td bgcolor="red"><img src="docs/relnotes_archive/titagline.gif"></td>
11 </tr>
12 </table>
13 <!-- Generated by Doxygen 1.5.1-p1 -->
14 <h1 align='center'><a name='XDC_TOP'></a>DSPLIB 3.0.0.8 Release Notes</h1>
15 <h2 align='center'>May 31, 2011</h2>
16 <h1>DSPLIB Bundle Release Notes</h1>
17 <p>
18 <hr>
19 <p>
20 <h2><a class="anchor" name="Contents"></a>Contents</h2>
21 <p>
22 <ol>
23 <li>
24 <a href="#Introduction">Introduction</a> </li>
25 <li>
26 <a href="#Starting">Getting Started</a> </li>
27 <li>
28 <a href="#Documentation">Documentation</a> <br>
29 </li>
30 <li>
31 <a href="#Whats_New">What's New</a> <br>
32 </li>
33 <li>
34 <a href="#Compatibility">Upgrade and Compatibility Information</a> <br>
35 </li>
36 <li>
37 <a href="#Device_Support">Device Support</a> <br>
38 </li>
39 <li>
40 <a href="#Validation">Validation Information</a> <br>
41 </li>
42 <li>
43 <a href="#Known_Issues">Known Issues</a> <br>
44 </li>
45 <li>
46 <a href="#Support">Technical Support</a> <br>
47 </li>
48 <li>
49 <a href="#Component">Component Release Notes</a> <br>
50 </li>
51 </ol>
52 <p>
53 <hr>
54 <p>
55 <h2><a class="anchor" name="Introduction"></a>Introduction</h2>
56 <p>
57 The DSPLIB bundle is an optimized DSP Function Library package together with the software tools (SWTOOLS) package in bundle format to simplify the release procedure.<p>
58 <hr>
59 <p>
60 <h2><a class="anchor" name="Starting"></a>Getting Started</h2>
61 <p>
62 The <a href="./docs/DSPLIB_Users_Manual.html">DSPLIB User's Manual</a> provides the documentation and references necessary to integrate DSPLIB Library routines into a development platform.<p>
63 <hr>
64 <p>
65 <h2><a class="anchor" name="Documentation"></a>Documentation</h2>
66 <p>
67 The following documentation is available:<p>
68 <table frame="box" rules="all" cellspacing="0" width="50%" border="1" cellpadding="3">
69 <tr>
70 <td valign="top"><b>User's Manual</b> </td><td align="center"><a href="./docs/DSPLIB_Users_Manual.html">[HTML]</a><br>
71 <a href="./docs/DSPLIB_Users_Manual.chm">[CHM]</a> </td></tr>
72 <tr>
73 <td valign="top"><b>Test Report</b> </td><td align="center"><a href="./docs/DSPLib_c66xTest_Report.html">[HTML]</a><br>
74 </td></tr>
75 <tr>
76 <td valign="top"><b>Software Manifest</b> </td><td align="center"><a href="./docs/DSPLIB_Software_Manifest.html">[HTML]</a><br>
77 </td></tr>
78 <tr>
79 <td valign="top"><b>Release Notes Archive</b> </td><td align="center"><a href="./docs/relnotes_archive">[LINK]</a> </td></tr>
80 </table>
81 <p>
82 <hr>
83 <p>
84 <h2><a class="anchor" name="Whats_New"></a>What's New</h2>
85 <p>
86 The following new features were added: <ol>
87 <li>
88 N/A </li>
89 </ol>
90 <p>
91 The following bugs have been resolved: <ol>
92 <li>
93 Fixed FFT16x32 twiddle factor access bug (IR #081234) </li>
94 </ol>
95 <p>
96 <hr>
97 <p>
98 <h2><a class="anchor" name="Compatibility"></a>Upgrade and Compatibility Information</h2>
99 <p>
100 This version of <b>DSPLIB</b> is compatible with the last released version:<p>
101 <table rules="all" frame="box" cellspacing="2" cellpadding="2" frame="void" width="10%" border="1">
102 <tr>
103 <th bgcolor="#cccccc">YES </th><td align="center"><b>X</b> </td></tr>
104 <tr>
105 <th bgcolor="#cccccc">NO </th><td align="center"><b></b> </td></tr>
106 </table>
107 <p>
108 <table bgcolor="#ffff99" frame="box" rules="none" cellspacing="0" width="80%" border="1" cellpadding="3">
109 <tr>
110 <td valign="top"><b>Note:</b> </td><td><ol>
111 <li>
112 Package compatibility keys are independent of component release versions. For more information visit: <a href="#VersionCompat">Package Versioning and Compatibility</a> </li>
113 </ol>
114 </td></tr>
115 </table>
116 <p>
117 <hr>
118 <p>
119 <h2><a class="anchor" name="Device_Support"></a>Device Support</h2>
120 <p>
121 This release supports the following device families:<p>
122 <ul>
123 <li>
124 C66x DSP (COFF, Little-Endian format) </li>
125 <li>
126 C66x DSP (COFF, Big-Endian format) </li>
127 <li>
128 C66x DSP (ELF, Little-Endian format) </li>
129 <li>
130 C66x DSP (ELF, Big-Endian format) </li>
131 </ul>
132 <p>
133 <hr>
134 <p>
135 <h2><a class="anchor" name="Validation"></a>Validation Information</h2>
136 <p>
137 This release was built and validated using the following tools:<p>
138 <ul>
139 <li>
140 XDC Tools version: 3.20.05.76 </li>
141 <li>
142 RTSC Packaging Standard version: 2.0 </li>
143 <li>
144 C6000 Code Generation Tools version: 7.2.0 </li>
145 <li>
146 Cose Composer Studio version: 4.2 </li>
147 <li>
148 GNU make version: 3.81 </li>
149 </ul>
150 <p>
151 <hr>
152 <p>
153 <h2><a class="anchor" name="Known_Issues"></a>Known Issues</h2>
154 <p>
155 <ol>
156 <li>
157 - C64x+ ELF support will be added in next release. </li>
158 </ol>
159 <p>
160 <hr>
161 <p>
162 <h2><a class="anchor" name="Support"></a>Technical Support</h2>
163 <p>
164 Questions regarding the DSPLIB library should be directed to the <a href="http://e2e.ti.com/support/embedded/f/355.aspx">Texas Instruments BIOS E2E Forum</a>. Please include the text "DSPLIB" in the title and add "C66x" and "DSPLIB" tags to your post.<p>
165 <hr>
166 <p>
167 <h2><a class="anchor" name="Component"></a>Component Release Notes</h2>
168 <p>
169 <ol>
170 <li>
171 <a href="./packages/ti/dsplib/dsplib_3_0_0_8_release_notes.html">DSPLIB Release Notes</a> </li>
172 </ol>
173 <p>
174 <hr>
175 <hr>
176 <p>
177 <h2><a class="anchor" name="VersionCompat"></a>Package Versioning and Compatibility</h2>
178 <p>
179 <h3>Compatibility Keys</h3>
180 <p>
181 Compatibility keys serve two primary purposes:<p>
182 <ol>
183 <li>
184 Enable tooling to identify incompatibilities between components </li>
185 <li>
186 Convey a level of compatibility between different releases to set end user expectations. </li>
187 </ol>
188 <p>
189 Each compatibility key is composed of 4 comma-delimited numbers - represented here by the letters M, S, R and P <code><b>[M,S,R,P]</b></code>. The table below provides a descriptive reference for compatibility key intention.<p>
190 <table rules="all" frame="box" cellspacing="2" cellpadding="2" frame="void" width="80%" border="1">
191 <caption align="bottom">Compatibility Key Reference</caption>
192 <tr valign="top" bgcolor="#cccccc">
193 <th width="10%">Key </th><th width="20%">Meaning </th><th width="70%">Description </th></tr>
194 <tr valign="top">
195 <td>1 (<b>M</b>=Major) </td><td>Break in compatibility </td><td>The package consumer is required to re-write the calling source code to use the package </td></tr>
196 <tr valign="top">
197 <td>2 (<b>S</b>=Source) </td><td>Source compatibility </td><td>The package consumer\92s source code doesn't require change, but does require a recompile </td></tr>
198 <tr valign="top">
199 <td>3 (<b>R</b>=Radix) </td><td>Introduction of new features </td><td>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 </td></tr>
200 <tr valign="top">
201 <td>4 (<b>P</b>=Patch) </td><td>Bug fixes only </td><td>If libraries are provided by the package, an application must re-link with the new libraries, but is not required to recompile its source. </td></tr>
202 </table>
203 <p>
204 <hr>
205 <p>
206 <h3>Versioning</h3>
207 <p>
208 Each package version is composed of 4 period-delimited numbers - represented here by the letters M, m, p and b <code><b>[M.m.p.b]</b></code>. The table below provides a descriptive reference regarding package version numbering.<p>
209 <table rules="all" frame="box" cellspacing="4" cellpadding="4" frame="void" width="80%" border="1">
210 <caption align="bottom">Package Version Reference</caption>
211 <tr valign="top" bgcolor="#cccccc">
212 <th width="10%">Digit </th><th width="20%">Meaning </th><th width="70%">Description </th></tr>
213 <tr valign="top">
214 <td>1 (<b>M</b>=Major) </td><td>Major revision </td><td>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. </td></tr>
215 <tr valign="top">
216 <td>2 (<b>m</b>=minor) </td><td>Minor revision </td><td>Incremented when the new version has changed but not in a major way. For example, some minor changes in the API or feature set. </td></tr>
217 <tr valign="top">
218 <td>3 (<b>p</b>=patch) </td><td>Patch number </td><td>Incremented for all other source code changes. This include any packaging support code. </td></tr>
219 <tr valign="top">
220 <td>4 (<b>b</b>=build) </td><td>Build number </td><td>Incremented for each release delivery to CM. Reset for any change to M, m or p </td></tr>
221 </table>
222 <hr size="1"><small>
223 Copyright 2011, Texas Instruments Incorporated</small>
224 </body>
225 </html>