1 | # |
---|
2 | # $Id$ |
---|
3 | # |
---|
4 | |
---|
5 | This is the list of outstanding problems in this release. |
---|
6 | |
---|
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. |
---|
9 | |
---|
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. |
---|
17 | |
---|
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. |
---|
22 | |
---|
23 | + Some of the BSPs still define RAM_START and RAM_END in the bsp.h file. |
---|
24 | It is better to define these in the linkcmds file. It is also nice |
---|
25 | to use the linkcmds file to place overlays for on-board hardware. |
---|
26 | |
---|
27 | + The __read() system call in all of the BSPs using single |
---|
28 | character input/output needs to be smarter. The following |
---|
29 | issues need to be addressed: |
---|
30 | |
---|
31 | + echoing of characters on input |
---|
32 | + CR/NL echoing |
---|
33 | + backspaces |
---|
34 | + tabs |
---|
35 | |
---|
36 | + UNIX port notes: |
---|
37 | |
---|
38 | + sometimes a stray SIGALRM is reported as spfatal completes. |
---|
39 | |
---|
40 | + There are conflicts between the names of native library routines |
---|
41 | which MUST be used and those in the POSIX support. This must |
---|
42 | be addressed. |
---|
43 | |
---|
44 | + Some of the tests may execute correctly and not produce the exact |
---|
45 | ordering of lines in the screen file. This appears to be a combination |
---|
46 | of a number of factors including buffering, processor speed, IO |
---|
47 | device overhead, and clock interrupt rate. |
---|
48 | |
---|
49 | + The compiler configuration files (c/make/gcc-XYZ.cfg) are largely |
---|
50 | the same when the different targets have the same CPU. It would |
---|
51 | be desirable to have a gcc-CPU.cfg or gcc-CPU_MODEL.cfg (e.g. |
---|
52 | gcc-m68k.cfg or gcc-m68020.cfg) and have the file gcc-TARGET.cfg |
---|
53 | include this and possibly override default settings. |
---|
54 | |
---|
55 | + The clock device drivers should really avoid doing the division |
---|
56 | by 1000 in the clock tick ISR to convert microseconds into |
---|
57 | milliseconds. This only applies to clock drivers which generate |
---|
58 | an ISR each millisecond and only call rtems_clock_tick every |
---|
59 | so many ISRs. |
---|