Changes between Version 369 and Version 370 of Developer/OpenProjects


Ignore:
Timestamp:
Feb 9, 2015, 2:07:04 PM (4 years ago)
Author:
Gedare Bloom
Comment:

Merge Joel's brain-dump

Legend:

Unmodified
Added
Removed
Modified
  • Developer/OpenProjects

    v369 v370  
    2424If one of these sounds interesting, ask on an RTEMS mailing list for details and we can all help scope the project. These are in absolutely no order. Do not think the order of this list is indicative of importance, size of project, or anything else. :)
    2525
    26 * Port RTEMS to Microblaze w/BSP for GDB simulator. Also eeds BSP for more complete HW on simulator.
    27 * Add recipes to RTEMS Source Builder for packages in rtems-addon-packages and graphics toolkit.
    28 * Add simulator recipes to RTEMS Tools for more simulators. Many more are supported by older simscripts.
    29 * Complete conversion of coverage reporting to Python and integration into RTEMS Tools. SOCIS 2014 code  works but is not production worthy. GCOV support could use work and generation of gcov reports as part of our output.
    30 * Add interface compliance tests for rest of POSIX API.
    31 * More peripherals for Raspberry Pi
    32 * Complete support for Edison
    33 * VESA x86 BIOS - This is Pavel Pisa's idea.
    34 * Continued work on RTEMS/Pok/VM effort.
    35 * rtems-testing and RSB improvements -run gcc tests
    36 * trace improvements and visualization
    37 
    3826= Testing =
    3927
     
    4836  *  Test the [wiki:Projects/POSIXFIFOs  POSIX FIFO Implementation].
    4937  *  [wiki:GSoC/2011/gprof  Add support for gprof output to covoar]
    50   *  ''Add [wiki:GSoC/2011/gcov  support for gcov output] to covoar so tools like gcov and lcov can be used with RTEMS ([wiki:Projects/GCOVSupport another page here])''
     38  *  ''Add [wiki:GSoC/2011/gcov  support for gcov output] to covoar so tools like gcov and lcov can be used with RTEMS ([wiki:Projects/GCOVSupport another page here])'' GCOV support could use work and generation of gcov reports as part of our output.
     39  * Complete conversion of coverage reporting to Python and integration into RTEMS Tools. SOCIS 2014 code works but is not production worthy.
    5140 *  [wiki:TBR/Delete/Fault_injection Fault tolerance]: get a fault injection tool to work with RTEMS and create tutorials and examples.
    5241 *  Improve [wiki:Projects/GNUToolsTesting  Testing of the GNU Tools] on RTEMS targets
    5342 *  ''[wiki:TBR/Delete/POSIXTimingTests  POSIX Timing Tests]''
    54  *  ''[wiki:Projects/POSIXComplianceTestSuite  POSIX Compliance Test Suite]''
     43 *  ''[wiki:Projects/POSIXComplianceTestSuite  POSIX Compliance Test Suite]'' Add interface compliance tests for rest of POSIX API.
    5544 *  [wiki:Projects/Open/SimulatorUpdates Simulator Updates] - Test BSPs that target simulators to find and fix problems. (SOCIS)
     45 * RTEMS Tester - rtems-test improvements. Add simulator recipes for more simulators. Many more are supported by older simscripts.
    5646
    5747= Tools and Development Environment =
     
    8474= Debugging =
    8575
    86  *  [wiki:Projects/TraceTool  Run-Time Tracing] - includes gathering, capturing, and displaying information to the user.
     76 *  [wiki:Projects/TraceTool  Run-Time Tracing] - includes gathering, capturing, and displaying information to the user.  We are looking for more trace improvements and visualization.
    8777 *  [wiki:Projects/CPU_Statistics CPU Statistics] - Improvements to CPU Usage Statistics. (SOCIS)
    8878 *  [wiki:Projects/Open/StackChecker Stack Checker] - Improvements to Stack Bounds Checker. (SOCIS)
    8979= Board Support Package (BSP) =
    9080
     81 * Port RTEMS to Microblaze (new architecture port, not just BSP) w/BSP for GDB simulator. Also needs BSP for more complete HW on simulator.
    9182 *  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.
    9283 *  We always welcome new BSPs for useful targets. Of special interest are readily available boards and open cores.
    9384 *  ''[wiki:Projects/MMU_Support  MMU Support]'' Implement MMU low-level support code for more BSPs.
    94  *  ''[wiki:TBR/BSP/Raspberry_Pi_BSP_Peripherals Raspberry Pi BSP Peripherals]'' Add peripheral support to the Raspberry Pi BSP.
     85 *  ''[wiki:TBR/BSP/Raspberry_Pi_BSP_Peripherals Raspberry Pi BSP Peripherals]'' Add peripheral support to the Raspberry Pi BSP. We still want more peripherals for Raspberry Pi
    9586 *  ''[wiki:Projects/GSoC/Beagle Beagle BSP improvements]'' - More peripherals for the Beagleboard / Beaglebone BSP and other improvements
     87 * VESA x86 BIOS - This is Pavel Pisa's idea.
     88 * x86 Edison
    9689
    9790= API Layers (POSIX, Classic, SAPI) =
     
    117110 *  Implement a [wiki:Projects/Open/LineEditor  Simple Line Editor].  Existing code can be refactored for a starting point.
    118111 *  ''[wiki:Dynamic_Object_File_Loading_  Dynamic Object File Loading (RTL)]'' lets a base application with RTEMS dynamically load the rest of the application. The dynamic parts can be optional features and never loaded, or upgraded replacements for parts of the application.
    119  *  '''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 toolkits in general. Here are the toolkits areas identified so far:
    120   *  Define a generic (Waf-based) infrastructure for building and maintaining toolkits.
     112 *  '''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 toolkits in general. The eventual goal is to have these toolkits buildable by the RTEMS Source Builder. Here are the toolkits areas identified so far:
     113  *  Define a generic (RTEMS Source Builder based) infrastructure for building and maintaining toolkits.
    121114  *  RTEMS Add ons - [http://git.rtems.org/rtems-addon-packages/ Add on packages] for RTEMS.
    122115  *  [wiki:Projects/BenchmarkKit RTEMS BenchKit] - benchmark programs for RTEMS