source: rtems/c/PROBLEMS @ 07058e7
Last change on this file since 07058e7 was 07058e7, checked in by Joel Sherrill <joel.sherrill@…>, on 09/27/95 at 21:08:30


  • Property mode set to 100644
File size: 2.3 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 m68000 support is nearly complete now.  The missing piece
11    inside the executive proper is support for the software interrupt
12    stack.  Also, the m68k family has become quite large and an
13    understanding of the compatibility of the peripherals on the various
14    members of the 683xx family would allow someone to designate some
15    of the drivers submitted for the gen683xx BSPs as useful on other
16    members.
18+   The only i960 family member tested is the CA.  No support for the
19    floating point support found in other family members is present.
20    This also implies that RTEMS may "think" of something as generic
21    across the i960 family when in fact it is specific to the CA.
23+   The __read() system call in all of the BSPs using single
24    character input/output needs to be smarter.  The following
25    issues need to be addressed:
27       + echoing of characters on input
28       + CR/NL echoing
29       + backspaces
30       + tabs
32+   UNIX port notes:
34       + sometimes a stray SIGALRM is reported as spfatal completes.
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.
40+   Some of the tests may execute correctly and not produce the exact
41    ordering of lines in the screen file.  This appears to be a combination
42    of a number of factors including buffering, processor speed, IO
43    device overhead, and clock interrupt rate.
45+   The compiler configuration files (c/make/gcc-XYZ.cfg) are largely
46    the same when the different targets have the same CPU.  It would
47    be desirable to have a gcc-CPU.cfg or gcc-CPU_MODEL.cfg (e.g.
48    gcc-m68k.cfg or gcc-m68020.cfg) and have the file gcc-TARGET.cfg
49    include this and possibly override default settings.
51+   The clock device drivers should really avoid doing the division
52    by 1000 in the clock tick ISR to convert microseconds into
53    milliseconds.  This only applies to clock drivers which generate
54    an ISR each millisecond and only call rtems_clock_tick every
55    so many ISRs.
Note: See TracBrowser for help on using the repository browser.