RTOS/rtems
1
0
Fork 0
forked from Imagelibrary/rtems
Code Pull Requests Activity

updated

Browse Source
This commit is contained in:
Joel Sherrill
1995-09-27 21:08:30 +00:00
parent 37f4c2d99f
commit 07058e75b4
1 changed files with 8 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
c/PROBLEMS
View File

@@ -4,12 +4,15 @@
This is the list of outstanding problems in this release. This is the list of outstanding problems in this release.
+ The m68000 support is not quite complete yet. The missing piece + The POSIX threads and real time extensions code in this tree does
not work yet and is intentionally not in the normal build path.
+ 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
understanding of the compatibility of the peripherals on the various understanding of the compatibility of the peripherals on the various
members of the 683xx family would allow someone to designate some members of the 683xx family would allow someone to designate some
of the drivers submitted for the gen68302 BSP as useful on other of the drivers submitted for the gen683xx BSPs as useful on other
members. members.
+ The only i960 family member tested is the CA. No support for the + The only i960 family member tested is the CA. No support for the
@@ -30,11 +33,9 @@ This is the list of outstanding problems in this release.
+ sometimes a stray SIGALRM is reported as spfatal completes. + sometimes a stray SIGALRM is reported as spfatal completes.
+ Currently the routines which need to make access to the + There are conflicts between the names of native library routines
native library (not newlib) are spread across a number of which MUST be used and those in the POSIX support. This must
directories. There should be a "unix_XYZ" wrapper for every be addressed.
one of these routines so there is only 1 directory which directly
references the "real" native library.
+ Some of the tests may execute correctly and not produce the exact + Some of the tests may execute correctly and not produce the exact
ordering of lines in the screen file. This appears to be a combination ordering of lines in the screen file. This appears to be a combination
@@ -52,9 +53,3 @@ This is the list of outstanding problems in this release.
milliseconds. This only applies to clock drivers which generate milliseconds. This only applies to clock drivers which generate
an ISR each millisecond and only call rtems_clock_tick every an ISR each millisecond and only call rtems_clock_tick every
so many ISRs. so many ISRs.
+ The MP code for the Message Manager copies the message buffer
in and out of the MPCI packet at at least two unecessary times:
+ as part of some send requests
+ on a non-successful receive response