Changes between Version 134 and Version 135 of Developer/OpenProjects

Timestamp:

01/26/10 02:35:22 (14 years ago)

Author:

JoelSherrill

Comment:

/* TinyRTEMS */ Move text to dedicated page

Developer/OpenProjects

@@ -139 +139 @@
 
 
-
-'''Status:''' Ongoing effort with multiple discrete projects.  Much progress has made on this goal since 4.7.0 but there is more shrinking left.  We are now to the point where the ARM/Thumb BSP rtl22xx_t and h8300/h8sim BSP have ~15K of code in the minimum.exe test.
-
-Reduce footprint of minimum RTEMS application.  We would like to be able to run on a CPU with only 64K ROM and 16K RAM.  This level of target hardware obviously is too small to host some RTEMS features.  
-
-Currently a minimum RTEMS application assumes that you want items like a shutdown code, initialization of all Classic API Managers, and support for c.  Some ideas in
-this area are captured at [wiki:Projects/TinyRTEMS TinyRTEMS].  The project would focus on breaking linkages between components so they can be configured out by 
-the user, dropped out automatically at link time, or other mechanisms.  The goal is to be able to provide the user with a full featured RTEMS
-library and defer as much configuration as possible to application configuration and link time.
-
-One issue that will be an ongoing concern is that the minimum footprint varies by BSP.  This is because some BSPs are structured to be lean, while others may have 
-unintentional dependencies.  One idea is a tool to assist in identifying RTEMS symbols which are not expected occur in some of the sample applications such minimum,
-hello, and ticker.  This utility could provide guidance on the known reasons this symbol creeps in.  For example, placing printk() support in the same file as
-the console driver will result in the entirety of the Termios subsystem being in the minimum footprint even though it is unused.
+See [wiki:Projects/TinyRTEMS TinyRTEMS] for details on the status of this project and remaining activities.
 = More NIC Drivers =