source: rtems/c/PROBLEMS @ 8fe6d358
Last change on this file since 8fe6d358 was 8a7fafb3, checked in by Joel Sherrill <joel.sherrill@…>, on 04/23/97 at 18:17:01

Updated to reflect changes since 3.6.0

  • Property mode set to 100644
File size: 2.5 KB
2#  $Id$
5This is the list of outstanding problems in this release.
7+   The shell scripts runtest and difftest do not work properly when
8    testing "debug" executables.
10+   AMD 29k port is based on a non-GNU toolset.
12+   The test spfatal is out of date and as a result will NOT execute
13    correctly.  The addition of POSIX and consequent ongoing initialization
14    reorganization makes it pointless to fix this until the POSIX support
15    is completely in place.
17+   The m68k family has become quite large and an understanding of the
18    compatibility of the peripherals on the various members of the 683xx
19    family would allow someone to designate some of the drivers submitted
20    for the gen683xx BSPs as useful on other members.
22+   The only supported i960 family member is the CA.  No support for the
23    floating point support found in other family members is present.
24    This also implies that RTEMS may "think" of something as generic
25    across the i960 family when in fact it is specific to the CA.
26    To make matters worse, the i960 target board owned by the RTEMS Project
27    is now broken and as a result even the i960CA is a "compile only" port.
29+   Some of the BSPs still define RAM_START and RAM_END in the bsp.h file.
30    It is better to define these in the linkcmds file.  It is also nice
31    to use the linkcmds file to place overlays for on-board hardware.
33+   The __read() system call in all of the BSPs using single
34    character input/output needs to be smarter.  The following
35    issues need to be addressed:
37       + echoing of characters on input
38       + CR/NL echoing
39       + backspaces
40       + tabs
42+   UNIX port notes:
44       + sometimes a stray SIGALRM is reported as spfatal completes.
46       + There are conflicts between the names of native library routines
47         which MUST be used and those in the POSIX support.  This must
48         be addressed.  The POSIX API cannot be used with this port as a
49         result of this.
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 clock device drivers should really avoid doing the division
57    by 1000 in the clock tick ISR to convert microseconds into
58    milliseconds.  This only applies to clock drivers which generate
59    an ISR each millisecond and only call rtems_clock_tick every
60    so many ISRs.
Note: See TracBrowser for help on using the repository browser.