Changeset 8a7fafb3 in rtems
- Timestamp:
- 04/23/97 18:17:01 (26 years ago)
- Branches:
- 4.10, 4.11, 4.8, 4.9, 5, master
- Children:
- 18647b7
- Parents:
- 7346e5f
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
c/PROBLEMS
r7346e5f r8a7fafb3 4 4 5 5 This is the list of outstanding problems in this release. 6 7 + The POSIX threads and real-time extensions are tested but this is8 the first release with them included. They are not enabled by9 default. The environment variable RTEMS_HAS_POSIX_API must be10 set to "yes" and the C language macro RTEMS_POSIX_API must be defined11 before this api is included in the build.12 6 13 7 + The shell scripts runtest and difftest do not work properly when … … 37 31 to use the linkcmds file to place overlays for on-board hardware. 38 32 39 + The __read(), __write(), etc. routines should be renamed __rtems_read(),40 etc. to avoid potential naming conflicts. [NOTE: This is already41 necessary under some versions of Linux with the unix port.]42 43 33 + The __read() system call in all of the BSPs using single 44 34 character input/output needs to be smarter. The following … … 56 46 + There are conflicts between the names of native library routines 57 47 which MUST be used and those in the POSIX support. This must 58 be addressed. 48 be addressed. The POSIX API cannot be used with this port as a 49 result of this. 59 50 60 51 + Some of the tests may execute correctly and not produce the exact … … 63 54 device overhead, and clock interrupt rate. 64 55 65 + The compiler configuration files (c/make/gcc-XYZ.cfg) are largely66 the same when the different targets have the same CPU. It would67 be desirable to have a gcc-CPU.cfg or gcc-CPU_MODEL.cfg (e.g.68 gcc-m68k.cfg or gcc-m68020.cfg) and have the file gcc-TARGET.cfg69 include this and possibly override default settings.70 71 56 + The clock device drivers should really avoid doing the division 72 57 by 1000 in the clock tick ISR to convert microseconds into
Note: See TracChangeset
for help on using the changeset viewer.