summaryrefslogtreecommitdiffstats
path: root/c/ACKNOWLEDGEMENTS
blob: 8e48dfd62bc1a3d84e55801883887219de4dc81e (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
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
#
#  $Id$
#

RTEMS was developed by On-Line Applications Research (OAR) under
contract to the U.S. Army Missile Command.  Other than the
contributions listed in this document, all code and documentation
was developed by OAR for the Army.

The RTEMS project would like to thank those who have made
contributions to the project.  Together we make RTEMS a
much better product.

The following persons/organizations have made contributions:

+ Dr. Mikhail (Misha) Savitski (mikhail.savitski@styrex.se) of the EISCAT
  Scientific Association submitted the BSP and other miscellaneous support
  for the Motorola MVME162 (M68040LC CPU) VMEbus single board computer.

+ Division Inc. of Chapel Hill, NC for sponsoring On-Line Applications
  Research to port RTEMS to the Hewlett-Packard PA-RISC architecture (V1.1)
  and the addition of HP-UX as a development host. Tony Bennett
  (tbennett@chapelhill.hp.com) was assisted in this effort by Joel Sherrill
  (joel@OARcorp.com).  Tony also deserves a big pat on the back for 
  contributing significantly to the overall organization of the development 
  environment and directory structure.  RTEMS is much easier to build 
  because of Tony.

+ Greg Allen of Division Inc. of Chapel Hill, NC for 
  porting RTEMS to HP-UX.  This port treats a UNIX computer as simply
  another RTEMS target processor.  This port can be used to develop 
  and test code which will ultimately run on the embedded platform.

+ Doug McBride (mcbride@rodin.colorado.edu) of the Colorado Space Grant
  College at the University of Colorado at Boulder submitted the BSP
  for the Motorola IDP board (M68EC040 CPU) single board computer.  The
  BSP leverages heavily off of the existing RTEMS BSP framework, the
  examples in the back of the IDP user's manual, and the libgloss example
  support for the IDP board from the newlib/libgloss distribution.

+ David Glessner (dwg@glenqcy.glenayre.com) of Glenayre Electronics
  submitted the support for the Motorola MC68302 CPU.  This included 
  the "gen68302" BSP which uses the on-chip peripherals on the MC68302 
  as well as the modifications to the m68k dependent executive code to 
  support m68k family members based on the mc68000 core.

+ Bryce Cogswell (cogswell@cs.uoregon.edu) submitted the support for MS-DOS 
  as a development environment as well as djgpp/go32 as a target environment.

+ Andy Bray (andy@chaos.org.uk) of I-CUBED Ltd. in Cambridge U.K.
  for porting RTEMS to the PowerPC.  This effort included support for the
  IBM 403 as well as the Motorola 601, 603, and 604 variants.  A special
  thanks to Dom Latter (dom@i-cubed.demon.co.uk) for being an RTEMS
  evangelist and promoting the use of RTEMS both at I-CUBED Ltd. as well  
  as within the Internet community as a whole.

+ John S. Gwynne (jsg@coulomb.eng.ohio-state.edu) of Ohio State University 
  submitted the support for the Motorola MC68332 CPU as well as completing 
  the support for CPUs based on the MC68000 core.  This included the "efi68k" 
  and "efi332" BSPs as well as completing the modifications to the m68k 
  dependent executive code to support m68k family members based on the 
  MC68000 core.  "efi68k" and "efi332" are single board computers designed 
  primarily for automotive electronic fuel injection (EFI) control, but can 
  be considered general purpose controllers when used without the EFI 
  companion board(s). See the README in each BSP for more information.

+ The European Space Agency for sponsoring On-Line Applications Research 
  to port RTEMS to the SPARC V7 architecture for use with their ERC32
  radiation-hardened CPU.  Jiri Gaisler (jgais@wd.estec.esa.nl) deserves
  special thanks for championing this port within the ESA was well as
  for developing and supporting the SPARC Instruction Simulator used to 
  develop and test this port.

+ Eric Norum (eric@skatter.usask.ca) of the Saskatchewan Accelerator
  Laboratory submitted the support for the Motorola MC68360 CPU
  including the `gen68360' BSP.

+ Dominique le Campion (Dominique.LECAMPION@enst-bretagne.fr), for
  Telecom Bretagne and T.N.I. (Brest, France) submitted the BSP for
  the Motorola MVME147 board (68030 CPU + 68881 FPU) and the MVME147s
  variant of this board.

+ Craig Lebakken (lebakken@minn.net) and Derrick Ostertag
  (ostertag@transition.com) of Transition Networks of Eden Prairie, MN
  for porting RTEMS to the MIPS and AMD 29K architectures.  This submission
  includes complete support for the R4650 as well as partial support
  for the R4600.

+ Erik Ivanenko (ccms@utcc.utoronto.ca) of the University of Toronto
  for submitting the i386ex bsp.

+ Jiri Gaisler (jgais@wd.estec.esa.nl) converted RTEMS to using GNU
  autoconf.  This effort is greatly appreciated.

+ Eric Norum (eric@skatter.usask.ca) of the Saskatchewan Accelerator
  Laboratory submitted a BSP for the m68360 when operating in companion
  mode with a m68040 and a port of the Motorola MC68040 Floating Point
  Support Package (FPSP) to RTEMS.

+ Eric Norum (eric@skatter.usask.ca) of the Saskatchewan Accelerator
  Laboratory submitted a port of the KA9Q TCP/IP stack to RTEMS as
  well as a network device driver for the gen68360 BSP.  To address
  performance issues and licensing concerns, Eric followed this up
  by replacing the KA9Q TCP/IP stack with a port of the FreeBSD stack.

+ Chris Johns (cjohns@plessey.com.au) submitted the ods68302 BSP which
  offers easier configuration than its counterpart gen68302.  Chris
  also submitted the RTEMS++ C++ class library and test code for
  that library.

+ Katsutoshi Shibuya (shibuya@mxb.meshnet.or.jp) of BU-Denken Co., Ltd. 
  (Sapporo, Japan) submitted the extended console driver for the 
  MVME162LX BSP and the POSIX tcsetattr() and tcgetattr() routines.
  This device driver supports four serial ports, cooked IO, and 
  provides a portable base for Zilog 8530 based console drivers.

+ Eric Norum (eric@skatter.usask.ca) and Katsutoshi Shibuya
  (shibuya@mxb.meshnet.or.jp) jointly developed the termios support.

+ Ralf Corsepius (corsepiu@faw.uni-ulm.de) of the Research Institute for
  Applied Knowledge Processing at the University of Ulm (FAW), Germany,
  for numerous enhancements to the RTEMS autoconf support as well as
  for the Hitachi SH port.

+ Dario Alcocer <alcocer@connectnet.com> submitted a port of the
  RTEMS port to FreeBSD.

+ David Fiddes <D.J.Fiddes@hw.ac.uk>, Rod Barman (rodb@ptgrey.com) and
  Stewart Kingdon (kingdon@ptgrey.com) submitted Motorola ColdFire
  support.  This work was supported in part by Real World Interface, Inc.

+ Geoffroy Montel (g_montel@yahoo.com), for CNET/DSM (Rennes, France),
  submitted the BSP for Motorola 68340/68349 based boards.

+ Thomas Doerfler (td@imd.m.isar.de) of IMD in 
  Puchheim,Germany submitted some improvements to the PPC403 
  support and added the helas403 BSP.

+ Jay Monkman (jmonkman@frasca.com) of Frasca International, Inc
  submitted the support for the Motorola MPC860 CPU including the
  'eth_comm' BSP

+ Charles Gauthier <Charles.Gauthier@iit.nrc.ca> of the Institute for
  Information Technology for the National Research Council of Canada
  submitted the Motorola MVME167 BSP.

+ Tony Ambardar (tonya@ece.ubc.ca) at the University of British Columbia
  ported RTEMS to the TS-1325 embedded PC from Technologic Systems
  (http://www.t-systems.com), and provided patches to enable software
  floating-point emulation for x86 targets. 

Finally, the RTEMS project would like to thank those who have contributed
to the other free software efforts which RTEMS utilizes.  The primary RTEMS
development environment is from the Free Software Foundation (the GNU
project).  The "newlib" C library was put together by Cygnus and is
a collaboration of the efforts of numerous individuals and organizations.

We would like to see your name here.  BSPs and ports are always welcome.
Useful libraries which support RTEMS applications are also an important
part of providing a strong foundation for the development of real-time
embedded applications and are welcome as submission.