Changes between Version 287 and Version 288 of Developer/OpenProjects

Timestamp:

02/06/13 21:24:37 (11 years ago)

Author:

Gedare

Comment:

Developer/OpenProjects

@@ -41 +41 @@
  *  [wiki:Projects/TCP/IP_update  Update the RTEMS TCP/IP stack] - The networking stack is old and showing it. This project actively underway.  At a high level, this effort requires porting the TCP/IP stack and providing support functional equivalents of multiple BSD kernel constructs.  This project has many subprojects many of which are appropriate for SOC. It would be of great usefulness to the community to get as many of these does as an SOC project as possible.
  *  RTEMS Toolkits - We are defining collections of libraries and support programs which make it easier to get started for certain types of applications.  We haven't identified all potential toolkits or components.  Each potential component must be evaluated for license and appropriateness for use in an embedded environment like RTEMS.  We also should define some guidelines about creating and maintaining these kits. Here are the toolkits areas identified so far:
+  *  [wiki:Projects/BenchmarkKit RTEMS BenchKit] - benchmark programs for RTEMS
   *  [wiki:Projects/ApplicationConfigurationKit RTEMS ConfigKit] - configuration file parsing libraries
   *  [wiki:Projects/DatabaseKit RTEMS DBKit] - database packages
@@ -55 +56 @@
 
  *  [wiki:Projects/TestingImprovements RTEMS Testing]. Testing for RTEMS, including Unit, Regression operational and building a custom test harness.  No prior knowledge of software testing is required.
+ *  [wiki:RTEMS_Test_Coverage  Test Coverage Analysis] - Improve coverage by adding more test cases. Eliminating dead code and reaching 100% coverage helps reduce the likelihood of new and recurrent bugs.
  *  Test the [wiki:Projects/POSIXFIFOs  POSIX FIFO Implementation].
  *  [wiki:RTEMSgprof_  Add support for gprof output to covoar]
  *  Improve [wiki:Projects/GNUToolsTesting  Testing of the GNU Tools] on RTEMS targets
- *  [wiki:Projects/BenchmarkKit RTEMS BenchKit] - benchmark programs for RTEMS
 = Development Environment Oriented =
 
@@ -85 +86 @@
 
  *  Unified Interrupt and PCI APIs -- [wiki:UnifiedAPIs UnifiedAPIs]
- *  Use [wiki:UseHashOrMapInNotepadsAndKeys_  Maps or Hashes] in the implementation of Classic API Notepads and POSIX API Keys. 
  *  RTEMS can always use [wiki:TBR/Delete/MoreBSPsForSimulators  more BSPs for Simulators].  Being able to test, debug, and perform coverage analysis on simulators is critical to the ongoing success of the project.
  *  Identify and implement the functionality currently missing in ''dup()''
@@ -102 +102 @@
 The following projects have had some work on them but are not complete. Ask about the current progress on the mailing list.  The remaining activities could be large or small:
 
- *  [wiki:RTEMS_Paravirtualization_  Paravirtualization] of RTEMS to make it suitable to be run as a guest OS in a hypervisor.
- *  [wiki:MMU_Support_  MMU Support] for RTEMS.
  *  [wiki:Projects/TinyRTEMS TinyRTEMS] is an umbrella term that corresponds to any activities or ideas that could shrink the code and data space requirements for RTEMS.  The goal is to progressively lower the minimum CPU requirements.
  *  Improve the RTEMS [wiki:SuperCore_Scheduler_  SuperCore Scheduler] - near complete
@@ -122 +120 @@
 The following projects have been worked on and the pages require updating.  There may or may not be enough work remaining to constitute an SOC project; many of these are past SOC projects.  If you are interested in one of these, please ask on the mailing list or IRC.
 
+ *  [wiki:RTEMS_Paravirtualization_  Paravirtualization] of RTEMS to make it suitable to be run as a guest OS in a hypervisor.
+ *  [wiki:MMU_Support_  MMU Support] for RTEMS.
+ *  Use [wiki:UseHashOrMapInNotepadsAndKeys_  Maps or Hashes] in the implementation of Classic API Notepads and POSIX API Keys. 
  *  Implement [wiki:POSIX_Asynchronous_IO_  POSIX Asynchronous and List IO]
  *  [wiki:RTEMS_Trace_Tool_  Run-Time Tracing] - includes gathering, capturing, and displaying information to the user.