blob: 05f61f05cd13853851dcec422fdfb5ee6cd07079 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
|
#
# $Id$
#
This is the list of outstanding problems in this release.
+ AMD 29k port is based on a non-GNU toolset.
+ The test spfatal is out of date and as a result will NOT execute
correctly. The addition of POSIX and consequent ongoing initialization
reorganization makes it pointless to fix this until the POSIX support
is completely in place.
+ The m68k family has become quite large and an understanding of the
compatibility of the peripherals on the various members of the 683xx
family would allow someone to designate some of the drivers submitted
for the gen683xx BSPs as useful on other members.
+ The only supported i960 family member is the CA. No support for the
floating point support found in other family members is present.
This also implies that RTEMS may "think" of something as generic
across the i960 family when in fact it is specific to the CA.
To make matters worse, the i960 target board owned by the RTEMS Project
is now broken and as a result even the i960CA is a "compile only" port.
+ Some of the BSPs still define RAM_START and RAM_END in the bsp.h file.
It is better to define these in the linkcmds file. It is also nice
to use the linkcmds file to place overlays for on-board hardware.
+ Not all of the BSP console drivers have been converted to termios.
Look at the m68k/gen68360, sparc/erc32, and powerpc/psim BSPs for
examples.
+ UNIX port notes:
+ sometimes a stray SIGALRM is reported as spfatal completes.
+ There are conflicts between the names of native library routines
which MUST be used and those in the POSIX support. This must
be addressed. The POSIX API cannot be used with this port as a
result of this.
+ Some of the tests may execute correctly and not produce the exact
ordering of lines in the screen file. This appears to be a combination
of a number of factors including buffering, processor speed, IO
device overhead, and clock interrupt rate. The biggest problem is that
some tests depend on polled IO with no unexpected context switches.
These may not be resolvable while maintaining the spirit of the test.
+ The clock device drivers should really avoid doing the division
by 1000 in the clock tick ISR to convert microseconds into
milliseconds. This only applies to clock drivers which generate
an ISR each millisecond and only call rtems_clock_tick every
so many ISRs.
+ Cross-check configure --enable-* flags.
+ warn/refuse to configure when --enable-libcdir and
--enable-gcc28 are given.
+ force --enable-libcdir when --disable-gcc28 is given
|
