Imagelibrary/rtems
1
0
Fork 1
mirror of https://gitlab.rtems.org/rtems/rtos/rtems.git synced 2025-12-05 15:15:44 +00:00
Code Issues Packages Projects Releases Wiki Activity

updated for 3.5.1

Browse Source
This commit is contained in:
Joel Sherrill
1996-01-19 22:16:53 +00:00
parent 84147e4fe4
commit d1c00a18cb
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
c/PROBLEMS
View File

@@ -7,6 +7,11 @@ This is the list of outstanding problems in this release.
+ The POSIX threads and real time extensions code in this tree does + The POSIX threads and real time extensions code in this tree does
not work yet and is intentionally not in the normal build path. not work yet and is intentionally not in the normal build path.
+ The test spfatal is out of date and as a result will NOT execute
correctly. The addition of POSIX and consequent ongoing initialization
reorganization makes it pointless to fix this until the POSIX support
is completely in place.
+ The m68000 support is nearly complete now. The missing piece + The m68000 support is nearly complete now. The missing piece
inside the executive proper is support for the software interrupt inside the executive proper is support for the software interrupt
stack. Also, the m68k family has become quite large and an stack. Also, the m68k family has become quite large and an
@@ -19,6 +24,8 @@ This is the list of outstanding problems in this release.
floating point support found in other family members is present. floating point support found in other family members is present.
This also implies that RTEMS may "think" of something as generic This also implies that RTEMS may "think" of something as generic
across the i960 family when in fact it is specific to the CA. across the i960 family when in fact it is specific to the CA.
To make matters worse, the i960 target board owned by the RTEMS Project
is now broken and as a result even the i960CA is a "compile only" port.
+ Some of the BSPs still define RAM_START and RAM_END in the bsp.h file. + Some of the BSPs still define RAM_START and RAM_END in the bsp.h file.
It is better to define these in the linkcmds file. It is also nice It is better to define these in the linkcmds file. It is also nice