Changes between Initial Version and Version 1 of Release/4.10


Ignore:
Timestamp:
09/11/08 20:57:56 (16 years ago)
Author:
JoelSherrill
Comment:

First cut

Legend:

Unmodified
Added
Removed
Modified
  • Release/4.10

    v1 v1  
     1= 4.10 Release Notes =
     2
     3
     4Open Ideas are are: [wiki:RTEMS410Ideas RTEMS410Ideas]
     5
     6This page lists the changes and improvements that are planned and/or have been made to the RTEMS development source since the 4.9 release branch was made. As usual, there will be submissions that are not expected and incorporated as ready into the 4.10 releases. In keeping with project history, the feature set of the 4.10 release series will be largely be driven by user submissions and requests.
     7
     8<blockquote>
     9Any snapshots made during this development effort are numbered 4.9.99.x.
     10</blockquote>
     11
     12<blockquote>
     13The RTEMS project provides '''built tools sets''' that are available for download. For Linux the RPM package formater is support and avaliable from the [wiki:TBR/Website/APT/Yum_Repository APT/Yum Repository]. For Windows [wiki:TBR/UserManual/MinGW_Tools_for_Windows MinGW Executable Installers] are available.
     14</blockquote>
     15
     16If any changes or enhancements are missing in this list, feel free to add them.  After all, that's why this is a Wiki.
     17= Tool Improvements =
     18
     19 *  TBD
     20
     21 *  Thanks again to Ralf, it is possible to provide target specific versions of the development tools. This is important when GCC drops support for an old architecture or we are avoiding target specific bugs in a particular tool version. Nominally, most RTEMS targets will use the same tools and they have been upgraded to the following versions:
     22  *  autoconf 2.63
     23  *  automake 1.10.1
     24  *  binutils 2.19 (expected)
     25  *  gcc 4.4.x (expected) for C/C++ with newlib 1.16.0
     26  *  gdb 6.8
     27
     28The latest patch for each tools is in rtems/contrib/crossrpms/patches.
     29= RTEMS Improvements =
     30
     31In this section, we discuss public API level changes as well as improvements to the implementation of those API routines. 
     32
     33Public API changes usually fall into one of the following categories:
     34
     35 *  Addition of new methods
     36 *  Modifications to prototypes
     37 *  Deletion of obsoleted methods
     38
     39Implementation improvements usually fall into one of the following categories:
     40
     41 *  Algorithm improvements in execution time or memory usage
     42 *  Critical section reduction
     43= API Changes =
     44
     45  *  TBD
     46= API Implementation Improvements =
     47
     48 *  TBD
     49= Configuration Changes =
     50
     51 *  TBD
     52= RTEMS Shell Improvements =
     53
     54
     55The following improvements were made to the RTEMS Shell:
     56
     57 *  TBD
     58= General =
     59
     60
     61 *  TBD
     62
     63= BSPs and Device Drivers =
     64
     65
     66 *  General
     67  *  Consolidation of various ''bsp_cleanup()'' implementations and a general push for as many BSPs as possible to use shared implementations. [Effort underway]
     68  *  Conversion of (hopefully) all BSPs to use ''bsp_get_work_area()'' and let ''boot_card()'' allocate memory between the C Program Heap and RTEMS Workspace.
     69
     70 *  New BSPs
     71  *  TBD
     72
     73 *  Significant updates to existing BSPs
     74  *  TBD
     75
     76 *  Removal of obsoleted BSPs
     77  *  TBD
     78= Test Suites =
     79
     80
     81 *  TBD
     82= RTEMS API Changes =
     83
     84
     85This section covers the API changes between the 4.9 and 4.10 release series which are expected to have an impact on application source code.  This section does NOT cover additions to the API.
     86
     87 *  TBD
     88
     89=Changes Per Point Release=
     90
     91= Release 4.10.0 Changes =
     92
     93
     94When this happens, you will be the first to know. :)