1 | # |
---|
2 | # $Id$ |
---|
3 | # |
---|
4 | |
---|
5 | This is the list of outstanding problems in this release. |
---|
6 | |
---|
7 | + AMD 29k port is based on a non-GNU toolset. |
---|
8 | |
---|
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. |
---|
13 | |
---|
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. |
---|
18 | |
---|
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. |
---|
25 | |
---|
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. |
---|
29 | |
---|
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. |
---|
33 | |
---|
34 | + UNIX port notes: |
---|
35 | |
---|
36 | + sometimes a stray SIGALRM is reported as spfatal completes. |
---|
37 | |
---|
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. |
---|
42 | |
---|
43 | + Someone suggested writing a mini-system call interface to |
---|
44 | include with RTEMS which would eliminate name conflicts. This |
---|
45 | would allow the RTEMS POSIX API to be tested in this configuration. |
---|
46 | |
---|
47 | + Some of the tests may execute correctly and not produce the exact |
---|
48 | ordering of lines in the screen file. This appears to be a combination |
---|
49 | of a number of factors including buffering, processor speed, IO |
---|
50 | device overhead, and clock interrupt rate. The biggest problem is that |
---|
51 | some tests depend on polled IO with no unexpected context switches. |
---|
52 | These may not be resolvable while maintaining the spirit of the test. |
---|
53 | |
---|
54 | + The clock device drivers should really avoid doing the division |
---|
55 | by 1000 in the clock tick ISR to convert microseconds into |
---|
56 | milliseconds. This only applies to clock drivers which generate |
---|
57 | an ISR each millisecond and only call rtems_clock_tick every |
---|
58 | so many ISRs. |
---|
59 | |
---|
60 | + Cross-check configure --enable-* flags. |
---|
61 | + warn/refuse to configure when --enable-libcdir and |
---|
62 | --enable-gcc28 are given. |
---|
63 | + force --enable-libcdir when --disable-gcc28 is given |
---|
64 | |
---|
65 | + make profile does not currently work for a variety of reasons. Few |
---|
66 | BSPs include profile versions of the libraries in their bsp_specs |
---|
67 | file. There is no mechanism to sample data for gperf to process. |
---|
68 | All of this will need to be addressed before "make profile" is truly |
---|
69 | useful. |
---|
70 | |
---|
71 | + Bare BSP does not compile for all configurations yet. This is |
---|
72 | primarily due to libcpu support code assuming that the BSP has |
---|
73 | made something available which is not with a bare BSP. |
---|