source: rtems/c/PROBLEMS @ 414ab59
Last change on this file since 414ab59 was 414ab59, checked in by Joel Sherrill <joel.sherrill@…>, on Jun 24, 1998 at 2:51:09 PM


  • Property mode set to 100644
File size: 2.3 KB
2#  $Id$
5This is the list of outstanding problems in this release.
7+   AMD 29k port is based on a non-GNU toolset.
9+   The test spfatal is out of date and as a result will NOT execute
10    correctly.  The addition of POSIX and consequent ongoing initialization
11    reorganization makes it pointless to fix this until the POSIX support
12    is completely in place.
14+   The m68k family has become quite large and an understanding of the
15    compatibility of the peripherals on the various members of the 683xx
16    family would allow someone to designate some of the drivers submitted
17    for the gen683xx BSPs as useful on other members.
19+   The only supported i960 family member is the CA.  No support for the
20    floating point support found in other family members is present.
21    This also implies that RTEMS may "think" of something as generic
22    across the i960 family when in fact it is specific to the CA.
23    To make matters worse, the i960 target board owned by the RTEMS Project
24    is now broken and as a result even the i960CA is a "compile only" port.
26+   Some of the BSPs still define RAM_START and RAM_END in the bsp.h file.
27    It is better to define these in the linkcmds file.  It is also nice
28    to use the linkcmds file to place overlays for on-board hardware.
30+   Not all of the BSP console drivers have been converted to termios.
31    Look at the m68k/gen68360, sparc/erc32, and powerpc/psim BSPs for
32    examples.
34+   UNIX port notes:
36       + sometimes a stray SIGALRM is reported as spfatal completes.
38       + There are conflicts between the names of native library routines
39         which MUST be used and those in the POSIX support.  This must
40         be addressed.  The POSIX API cannot be used with this port as a
41         result of this.
43+   Some of the tests may execute correctly and not produce the exact
44    ordering of lines in the screen file.  This appears to be a combination
45    of a number of factors including buffering, processor speed, IO
46    device overhead, and clock interrupt rate.
48+   The clock device drivers should really avoid doing the division
49    by 1000 in the clock tick ISR to convert microseconds into
50    milliseconds.  This only applies to clock drivers which generate
51    an ISR each millisecond and only call rtems_clock_tick every
52    so many ISRs.
Note: See TracBrowser for help on using the repository browser.