![[RTEMS Logo]](/images/logo.png){kind=logo}
Changes between Version 20 and Version 21 of Release/4.6
- Timestamp:
- 03/19/17 22:37:50 (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Release/4.6
v20 v21 7 7 8 8 Release [wiki:4.6#Release_4.6.6_Changes 4.6.6] is the '''LAST PUBLIC RELEASE''' in the 4.6 release series from the RTEMS Project. 9 Legacy support for the 4.6 releases is available from [http://www.rtems. org/oarsupport/ OAR Corporation].9 Legacy support for the 4.6 releases is available from [http://www.rtems.com/ OAR Corporation]. 10 10 11 11 Release 4.6.6 of RTEMS is primarily a problem fixing release and the problems addressed are discussed here. The primary driving factor for [wiki:4.6#Release_4.6.6_Changes 4.6.6] was a patch to address GCC optimizing code outside of interrupt disable critical sections. Other bug fixes and improvements were also committed to the branch so this release includes them. The notable changes are that the SPARC LEON3 BSP received significant improvements including supprt for SpaceWire and a new NIC from Gaisler Research. The PC386 BSP was modified to allow easy compile time selection of VGA or COM1 as the console. 12 12 13 4.6.6 is available for download from ftp://ftp.rtems.com/pub/rtems/4.6.6 or http://www.rtems.com/ftp/pub/rtems/4.6.6.13 4.6.6 is available for download from https://ftp.rtems.org/pub/rtems/releases/4.6/4.6.6. 14 14 15 15 Please be warned that the entire set of tools for all hosts can consume an enormous amount of space. For the 4.6 series, this is approximately 1.6 GB. The bulk of this is tool binaries for approximately 10 target CPU families on GNU/Linux, Cygwin, and Solaris. It is highly unlikely that any non-maintainer requires a full download. Please try to download just what is required. … … 20 20 21 21 * Pre-built tools now installed into /opt/rtems-4.6 to avoid conflicts with tools from previous release series. 22 * All RPMs are now digitally signed to ensure their integrity and origin. The key is available for download from ftp://ftp.rtems. com/pub/rtems/gpg-pubkey-EAC29B6F.22 * All RPMs are now digitally signed to ensure their integrity and origin. The key is available for download from ftp://ftp.rtems.org/pub/rtems/gpg-pubkey-EAC29B6F. 23 23 * RPMs may be downloaded and updated using [wiki:APT/Yum_Repository_ APT or Yum] 24 24 * Tool binaries are available for: 25 * RedHat Gnu/Linux 7.3 and later -- ftp://ftp.rtems. com/pub/rtems/linux/redhat/7.3/i386/rpms/rtems-4.626 * all Fedora Core releases -- ftp://ftp.rtems. com/pub/rtems/linux/redhat/7.3/i386/rpms/rtems-4.627 * Cygwin -- ftp://ftp.rtems. com/pub/rtems/cygwin/rtems-4.628 * Solaris -- ftp://ftp.rtems. com/pub/rtems/solaris/rtems-4.625 * RedHat Gnu/Linux 7.3 and later -- ftp://ftp.rtems.org/pub/rtems/linux/redhat/7.3/i386/rpms/rtems-4.6 26 * all Fedora Core releases -- ftp://ftp.rtems.org/pub/rtems/linux/redhat/7.3/i386/rpms/rtems-4.6 27 * Cygwin -- ftp://ftp.rtems.org/pub/rtems/cygwin/rtems-4.6 28 * Solaris -- ftp://ftp.rtems.org/pub/rtems/solaris/rtems-4.6 29 29 = RTEMS Improvements = 30 30 … … 56 56 57 57 58 11 problems reports ( ftp://ftp.rtems.com/pub/rtems/4.6.6/PRs-closed-4.6.6) filed by users were closed between 4.6.5 and 4.6.6. Four (4) of these were BSP specific. These problems can be roughly categorized as follows:58 11 problems reports (https://ftp.rtems.org/pub/rtems/releases/4.6/4.6.6/PRs-closed-4.6.6) filed by users were closed between 4.6.5 and 4.6.6. Four (4) of these were BSP specific. These problems can be roughly categorized as follows: 59 59 60 60 * Run-Time Problems (7) … … 74 74 = Release 4.6.5 Changes = 75 75 76 6 problems reports ( ftp://ftp.rtems.com/pub/rtems/4.6.5/PRs-closed-4.6.5) filed by users were closed between 4.6.4 and 4.6.5. Five (5) of these were BSP specific and only one was cross-platform. These problems can be roughly categorized as follows:76 6 problems reports (https://ftp.rtems.org/pub/rtems/releases/4.6/4.6.5/PRs-closed-4.6.5) filed by users were closed between 4.6.4 and 4.6.5. Five (5) of these were BSP specific and only one was cross-platform. These problems can be roughly categorized as follows: 77 77 78 78 * Run-Time Problems (1) … … 86 86 = Release 4.6.4 Changes = 87 87 88 38 problems reported ( ftp://ftp.rtems.com/pub/rtems/4.6.4/PRs-closed-4.6.4) by users were fixed between 4.6.2 and 4.6.4. On a positive note, 3 of these issues were simple improvements in argument parsing, 8 were general improvements in either functionality or cleanup, and 12 were BSP or port specific. These problems can be roughly categorized as follows:88 38 problems reported (https://ftp.rtems.org/pub/rtems/releases/4.6/4.6.4/PRs-closed-4.6.4) by users were fixed between 4.6.2 and 4.6.4. On a positive note, 3 of these issues were simple improvements in argument parsing, 8 were general improvements in either functionality or cleanup, and 12 were BSP or port specific. These problems can be roughly categorized as follows: 89 89 90 90 * Improved Parameter Validation (3) … … 147 147 = Release 4.6.2 Changes = 148 148 149 37 problems reported ( ftp://ftp.rtems.com/pub/rtems/4.6.2/PRs-closed-4.6.2) by users were fixed between 4.6.1 and 4.6.2. On a positive note, 8 of these issues were simple improvements in argument parsing and 7 were general improvements in either functionality or cleanup. These problems can be categorized as follows:149 37 problems reported (https://ftp.rtems.org/pub/rtems/releases/4.6/4.6.2/PRs-closed-4.6.2) by users were fixed between 4.6.1 and 4.6.2. On a positive note, 8 of these issues were simple improvements in argument parsing and 7 were general improvements in either functionality or cleanup. These problems can be categorized as follows: 150 150 151 151 * Improved Parameter Validation (8) … … 196 196 = Release 4.6.1 Changes = 197 197 198 Fourteen problems reported ( ftp://ftp.rtems.com/pub/rtems/4.6.1/PRs-closed-4.6.1) by users were fixed between 4.6.0 and 4.6.1. These problems can be categorized as follows:198 Fourteen problems reported (https://ftp.rtems.org/pub/rtems/releases/4.6/4.6.1/PRs-closed-4.6.1) by users were fixed between 4.6.0 and 4.6.1. These problems can be categorized as follows: 199 199 200 200 * General Build Failures (1)
