source: rtems/c/PROBLEMS @ d1c00a18
Last change on this file since d1c00a18 was d1c00a18, checked in by Joel Sherrill <joel.sherrill@…>, on 01/19/96 at 22:16:53

updated for 3.5.1

  • Property mode set to 100644
File size: 2.9 KB
2#  $Id$
5This is the list of outstanding problems in this release.
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.
10+   The test spfatal is out of date and as a result will NOT execute
11    correctly.  The addition of POSIX and consequent ongoing initialization
12    reorganization makes it pointless to fix this until the POSIX support
13    is completely in place.
15+   The m68000 support is nearly complete now.  The missing piece
16    inside the executive proper is support for the software interrupt
17    stack.  Also, the m68k family has become quite large and an
18    understanding of the compatibility of the peripherals on the various
19    members of the 683xx family would allow someone to designate some
20    of the drivers submitted for the gen683xx BSPs as useful on other
21    members.
23+   The only i960 family member tested is the CA.  No support for the
24    floating point support found in other family members is present.
25    This also implies that RTEMS may "think" of something as generic
26    across the i960 family when in fact it is specific to the CA.
27    To make matters worse, the i960 target board owned by the RTEMS Project
28    is now broken and as a result even the i960CA is a "compile only" port.
30+   Some of the BSPs still define RAM_START and RAM_END in the bsp.h file.
31    It is better to define these in the linkcmds file.  It is also nice
32    to use the linkcmds file to place overlays for on-board hardware.
34+   The __read() system call in all of the BSPs using single
35    character input/output needs to be smarter.  The following
36    issues need to be addressed:
38       + echoing of characters on input
39       + CR/NL echoing
40       + backspaces
41       + tabs
43+   UNIX port notes:
45       + sometimes a stray SIGALRM is reported as spfatal completes.
47       + There are conflicts between the names of native library routines
48         which MUST be used and those in the POSIX support.  This must
49         be addressed.
51+   Some of the tests may execute correctly and not produce the exact
52    ordering of lines in the screen file.  This appears to be a combination
53    of a number of factors including buffering, processor speed, IO
54    device overhead, and clock interrupt rate.
56+   The compiler configuration files (c/make/gcc-XYZ.cfg) are largely
57    the same when the different targets have the same CPU.  It would
58    be desirable to have a gcc-CPU.cfg or gcc-CPU_MODEL.cfg (e.g.
59    gcc-m68k.cfg or gcc-m68020.cfg) and have the file gcc-TARGET.cfg
60    include this and possibly override default settings.
62+   The clock device drivers should really avoid doing the division
63    by 1000 in the clock tick ISR to convert microseconds into
64    milliseconds.  This only applies to clock drivers which generate
65    an ISR each millisecond and only call rtems_clock_tick every
66    so many ISRs.
Note: See TracBrowser for help on using the repository browser.