Changeset 07058e7 in rtems
- Timestamp:
- 09/27/95 21:08:30 (28 years ago)
- Branches:
- 4.10, 4.11, 4.8, 4.9, 5, master
- Children:
- 1039ae4
- Parents:
- 37f4c2d
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
c/PROBLEMS
r37f4c2d r07058e7 5 5 This is the list of outstanding problems in this release. 6 6 7 + The m68000 support is not quite complete yet. The missing piece 7 + The POSIX threads and real time extensions code in this tree does 8 not work yet and is intentionally not in the normal build path. 9 10 + The m68000 support is nearly complete now. The missing piece 8 11 inside the executive proper is support for the software interrupt 9 12 stack. Also, the m68k family has become quite large and an 10 13 understanding of the compatibility of the peripherals on the various 11 14 members of the 683xx family would allow someone to designate some 12 of the drivers submitted for the gen683 02 BSPas useful on other15 of the drivers submitted for the gen683xx BSPs as useful on other 13 16 members. 14 17 … … 31 34 + sometimes a stray SIGALRM is reported as spfatal completes. 32 35 33 + Currently the routines which need to make access to the 34 native library (not newlib) are spread across a number of 35 directories. There should be a "unix_XYZ" wrapper for every 36 one of these routines so there is only 1 directory which directly 37 references the "real" native library. 36 + There are conflicts between the names of native library routines 37 which MUST be used and those in the POSIX support. This must 38 be addressed. 38 39 39 40 + Some of the tests may execute correctly and not produce the exact … … 53 54 an ISR each millisecond and only call rtems_clock_tick every 54 55 so many ISRs. 55 56 + The MP code for the Message Manager copies the message buffer57 in and out of the MPCI packet at at least two unecessary times:58 59 + as part of some send requests60 + on a non-successful receive response
Note: See TracChangeset
for help on using the changeset viewer.