source: rtems/c/PROBLEMS @ b7acc57f
Last change on this file since b7acc57f was b7acc57f, checked in by Joel Sherrill <joel.sherrill@…>, on 07/02/96 at 17:46:34

updated to reflect 3.5.17

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