1 | # |
---|
2 | # $Id$ |
---|
3 | # |
---|
4 | |
---|
5 | RTEMS was developed by On-Line Applications Research (OAR) under |
---|
6 | contract to the U.S. Army Missile Command. Other than the |
---|
7 | contributions listed in this document, all code and documentation |
---|
8 | was developed by OAR for the Army. |
---|
9 | |
---|
10 | The RTEMS project would like to thank those who have made |
---|
11 | contributions to the project. Together we make RTEMS a |
---|
12 | much better product. |
---|
13 | |
---|
14 | The following persons/organizations have made contributions: |
---|
15 | |
---|
16 | + Dr. Mikhail (Misha) Savitski (mikhail.savitski@styrex.se) of the EISCAT |
---|
17 | Scientific Association submitted the BSP and other miscellaneous support |
---|
18 | for the Motorola MVME162 (M68040LC CPU) VMEbus single board computer. |
---|
19 | |
---|
20 | + Division Inc. of Chapel Hill, NC for sponsoring On-Line Applications |
---|
21 | Research to port RTEMS to the Hewlett-Packard PA-RISC architecture (V1.1) |
---|
22 | and the addition of HP-UX as a development host. Tony Bennett |
---|
23 | (tbennett@chapelhill.hp.com) was assisted in this effort by Joel Sherrill |
---|
24 | (joel@OARcorp.com). Tony also deserves a big pat on the back for |
---|
25 | contributing significantly to the overall organization of the development |
---|
26 | environment and directory structure. RTEMS is much easier to build |
---|
27 | because of Tony. |
---|
28 | |
---|
29 | + Greg Allen of Division Inc. of Chapel Hill, NC for |
---|
30 | porting RTEMS to HP-UX. This port treats a UNIX computer as simply |
---|
31 | another RTEMS target processor. This port can be used to develop |
---|
32 | and test code which will ultimately run on the embedded platform. |
---|
33 | |
---|
34 | + Doug McBride (mcbride@rodin.colorado.edu) of the Colorado Space Grant |
---|
35 | College at the University of Colorado at Boulder submitted the BSP |
---|
36 | for the Motorola IDP board (M68EC040 CPU) single board computer. The |
---|
37 | BSP leverages heavily off of the existing RTEMS BSP framework, the |
---|
38 | examples in the back of the IDP user's manual, and the libgloss example |
---|
39 | support for the IDP board from the newlib/libgloss distribution. |
---|
40 | |
---|
41 | + David Glessner (dwg@glenqcy.glenayre.com) of Glenayre Electronics |
---|
42 | submitted the support for the Motorola MC68302 CPU. This included |
---|
43 | the "gen68302" BSP which uses the on-chip peripherals on the MC68302 |
---|
44 | as well as the modifications to the m68k dependent executive code to |
---|
45 | support m68k family members based on the mc68000 core. |
---|
46 | |
---|
47 | + Bryce Cogswell (cogswell@cs.uoregon.edu) submitted the support for MS-DOS |
---|
48 | as a development environment as well as djgpp/go32 as a target environment. |
---|
49 | |
---|
50 | + Andy Bray (andy@chaos.org.uk) of I-CUBED Ltd. in Cambridge U.K. |
---|
51 | for porting RTEMS to the PowerPC. This effort included support for the |
---|
52 | IBM 403 as well as the Motorola 601, 603, and 604 variants. A special |
---|
53 | thanks to Dom Latter (dom@i-cubed.demon.co.uk) for being an RTEMS |
---|
54 | evangelist and promoting the use of RTEMS both at I-CUBED Ltd. as well |
---|
55 | as within the Internet community as a whole. |
---|
56 | |
---|
57 | + John S. Gwynne (jsg@coulomb.eng.ohio-state.edu) of Ohio State University |
---|
58 | submitted the support for the Motorola MC68332 CPU as well as completing |
---|
59 | the support for CPUs based on the MC68000 core. This included the "efi68k" |
---|
60 | and "efi332" BSPs as well as completing the modifications to the m68k |
---|
61 | dependent executive code to support m68k family members based on the |
---|
62 | MC68000 core. "efi68k" and "efi332" are single board computers designed |
---|
63 | primarily for automotive electronic fuel injection (EFI) control, but can |
---|
64 | be considered general purpose controllers when used without the EFI |
---|
65 | companion board(s). See the README in each BSP for more information. |
---|
66 | |
---|
67 | + The European Space Agency for sponsoring On-Line Applications Research |
---|
68 | to port RTEMS to the SPARC V7 architecture for use with their ERC32 |
---|
69 | radiation-hardened CPU. Jiri Gaisler (jgais@wd.estec.esa.nl) deserves |
---|
70 | special thanks for championing this port within the ESA was well as |
---|
71 | for developing and supporting the SPARC Instruction Simulator used to |
---|
72 | develop and test this port. |
---|
73 | |
---|
74 | + Eric Norum (eric@skatter.usask.ca) of the Saskatchewan Accelerator |
---|
75 | Laboratory submitted the support for the Motorola MC68360 CPU |
---|
76 | including the `gen68360' BSP. |
---|
77 | |
---|
78 | + Dominique le Campion (Dominique.LECAMPION@enst-bretagne.fr), for |
---|
79 | Telecom Bretagne and T.N.I. (Brest, France) submitted the BSP for |
---|
80 | the Motorola MVME147 board (68030 CPU + 68881 FPU) and the MVME147s |
---|
81 | variant of this board. |
---|
82 | |
---|
83 | + Craig Lebakken (lebakken@minn.net) and Derrick Ostertag |
---|
84 | (ostertag@transition.com) of Transition Networks of Eden Prairie, MN |
---|
85 | for porting RTEMS to the MIPS and AMD 29K architectures. This submission |
---|
86 | includes complete support for the R4650 as well as partial support |
---|
87 | for the R4600. |
---|
88 | |
---|
89 | + Erik Ivanenko (ccms@utcc.utoronto.ca) of the University of Toronto |
---|
90 | for submitting the i386ex bsp. |
---|
91 | |
---|
92 | + Jiri Gaisler (jgais@wd.estec.esa.nl) converted RTEMS to using GNU |
---|
93 | autoconf. This effort is greatly appreciated. |
---|
94 | |
---|
95 | + Eric Norum (eric@skatter.usask.ca) of the Saskatchewan Accelerator |
---|
96 | Laboratory submitted a BSP for the m68360 when operating in companion |
---|
97 | mode with a m68040 and a port of the Motorola MC68040 Floating Point |
---|
98 | Support Package (FPSP) to RTEMS. |
---|
99 | |
---|
100 | + Eric Norum (eric@skatter.usask.ca) of the Saskatchewan Accelerator |
---|
101 | Laboratory submitted a port of the KA9Q TCP/IP stack to RTEMS as |
---|
102 | well as a network device driver for the gen68360 BSP. |
---|
103 | |
---|
104 | + Chris Johns (cjohns@plessey.com.au) submitted the ods68302 BSP which |
---|
105 | offers easier configuration than its counterpart gen68302. Chris |
---|
106 | also submitted the RTEMS++ C++ class library and test code for |
---|
107 | that library. |
---|
108 | |
---|
109 | + Katsutoshi Shibuya (shibuya@mxb.meshnet.or.jp) of BU-Denken Co., Ltd. |
---|
110 | (Sapporo, Japan) submitted the extended console driver for the |
---|
111 | MVME162LX BSP and the POSIX tcsetattr() and tcgetattr() routines. |
---|
112 | This device driver supports four serial ports, cooked IO, and |
---|
113 | provides a portable base for Zilog 8530 based console drivers. |
---|
114 | |
---|
115 | + Eric Norum (eric@skatter.usask.ca) and Katsutoshi Shibuya |
---|
116 | (shibuya@mxb.meshnet.or.jp) jointly developed the termios support. |
---|
117 | |
---|
118 | + Ralf Corsepius (corsepiu@faw.uni-ulm.de) of the Research Institute for |
---|
119 | Applied Knowledge Processing at the University of Ulm (FAW), Germany, |
---|
120 | for numerous enhancements to the RTEMS autoconf support as well as |
---|
121 | for the Hitachi SH port. |
---|
122 | |
---|
123 | Finally, the RTEMS project would like to thank those who have contributed |
---|
124 | to the other free software efforts which RTEMS utilizes. The primary RTEMS |
---|
125 | development environment is from the Free Software Foundation (the GNU |
---|
126 | project). The "newlib" C library was put together by Cygnus and is |
---|
127 | a collaboration of the efforts of numerous individuals and organizations. |
---|
128 | |
---|
129 | We would like to see your name here. BSPs and ports are always welcome. |
---|
130 | Useful libraries which support RTEMS applications are also an important |
---|
131 | part of providing a strong foundation for the development of real-time |
---|
132 | embedded applications and are welcome as submission. |
---|
133 | |
---|