Changes between Version 194 and Version 195 of Developer/OpenProjects
- Timestamp:
- 02/10/11 23:51:15 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Developer/OpenProjects
v194 v195 38 38 The following projects have no work on them. 39 39 40 * Implement [wiki:POSIX_Asynchronous_IO_ POSIX Asynchronous and List IO]40 * Unified Interrupt and PCI APIs -- [wiki:UnifiedAPIs UnifiedAPIs] 41 41 * Use [wiki:UseHashOrMapInNotepadsAndKeys_ Maps or Hashes] in the implementation of Classic API Notepads and POSIX API Keys. 42 42 * 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. … … 46 46 * [wiki:Projects/SystemEvents RTEMS System Events] is a project to add a first class object for events. Currently all event sets are tied to a specific thread. 47 47 * Implement OSEK Support [http://portal.osek-vdx.org/] 48 * Implement current version of µITRON Interface [http://www.www.tron.org/index-e.html] 49 * Unified Interrupt and PCI APIs -- [wiki:UnifiedAPIs UnifiedAPIs] 48 50 49 * Port Transparent IPC (http://tipc.sourceforge.net/index.html) to RTEMS 51 50 * Merge BSP for Simplescalar simulator -- http://www.jwhitham.org.uk/simplescalar/ 52 * Support for new Processor Families - Microblaze, Xtensa,Cortex/Thumb-2?51 * Support for new Processor Families - Xtensa, Cortex/Thumb-2, Microblaze 53 52 * [wiki:GSoC/2011/ISO9660_Filesystem ISO9660 file system] 54 53 * Add cache manager support for architectures not having it. … … 56 55 * Port RTEMS to a [http://www.xen.org/ Xen] or other hypervisor environment. 57 56 * [wiki:Projects/Refactor_the_filesystem_infrastructure Refactor the filesystem infrastructure] 57 * Implement current version of µITRON Interface [http://www.www.tron.org/index-e.html] 58 58 = Run-Time Projects With Some Work = 59 59 … … 61 61 The following projects have had some work on them but are not complete. The remaining activities could be large or small: 62 62 63 * [wiki:RTEMS_Trace_Tool_ Run-Time Tracing] - includes gathering, capturing, and displaying information to the user.64 63 * [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. 65 64 * [wiki:MMU_Support_ MMU Support] for RTEMS. This has had some work. See that page for status. 66 * [wiki:Projects/SequencedInitialization RTEMS Sequenced Initialization] is a project to allow RTEMS initialization to be dynamically constructed based upon user requirements. It would be like C++ global constructors conceptually.67 * [wiki:Projects/libdl Dynamic Object File Loading] is an important feature for many types of embedded applications. It lets you have a base application with RTEMS which dynamically loads the rest of the application. The dynamic parts can be optional features and never loaded. Plus they are more easily upgraded than an entire application image.68 65 * Various projects to port BSD system components. In addition to general issues about integrating BSD code into RTEMS, there are specific status and issues for each of the individual projects. Details on each project are below: 69 66 * [http://code.google.com/p/rosetta-os Rosetta OS] [wiki:Projects/RosettaOSDeviceDriverAPI OS Independent Device Driver API] 70 67 * more [wiki:TBR/Delete/Libbsd-port NIC device drivers] 71 68 * [wiki:Projects/TCP/IP_update update the RTEMS TCP/IP stack] 72 * [wiki:TBR/UserManual/USBStack port BSD USB stack] 69 70 = Projects Requiring Update = 71 72 73 The following projects have been worked on and the pages require updating. 74 73 75 * Refactor RTEMS scheduler to a modular [wiki:SuperCore_Scheduler_ SuperCore Scheduler] 74 75 * TBD Move other descriptions to their own page and list here. Shorten master page. 76 * Implement [wiki:POSIX_Asynchronous_IO_ POSIX Asynchronous and List IO] 77 * [wiki:RTEMS_Trace_Tool_ Run-Time Tracing] - includes gathering, capturing, and displaying information to the user. 78 * [wiki:Projects/SequencedInitialization RTEMS Sequenced Initialization] is a project to allow RTEMS initialization to be dynamically constructed based upon user requirements. It would be like C++ global constructors conceptually. 79 * [wiki:Projects/libdl Dynamic Object File Loading] is an important feature for many types of embedded applications. It lets you have a base application with RTEMS which dynamically loads the rest of the application. The dynamic parts can be optional features and never loaded. Plus they are more easily upgraded than an entire application image. 80 * [wiki:TBR/UserManual/USBStack port BSD USB stack] 81 * [wiki:Projects/Parrot Parrot On RTEMS] 82 * RTEMS port of [wiki:Projects/GCCGoRTEMS GNU GCC Go] 76 83 = Third Party Packages = 77 84 … … 81 88 * See the [wiki:Projects/GraphicsToolkit RTEMS Graphics Toolkit] for current status of the kit and ideas for future work. 82 89 * Integrate [wiki:Projects/CEXP CEXP] into main RTEMS distribution. 83 * [wiki:Projects/Parrot Parrot On RTEMS]84 90 * [wiki:Projects/Mono Mono On RTEMS] 85 91 * Turn the current port of [wiki:Packages/LWIP LWIP] into a first class citizen. Submit port, make target independent, etc. … … 117 123 The following projects are about general improvements to the development environment. 118 124 119 * RTEMS port of [wiki:Projects/GCCGoRTEMS GNU GCC Go]120 125 * Improve [wiki:Projects/GNUToolsTesting Testing of the GNU Tools] on RTEMS targets 121 126 * RTEMS port of the [[GNUJavaCompiler| GNU Java Compiler (gjc)]]