source: rtems/c/ACKNOWLEDGEMENTS @ c499856

4.11
Last change on this file since c499856 was 65c6425, checked in by Joel Sherrill <joel.sherrill@…>, on May 3, 2012 at 5:24:46 PM

Remove CVS Id Strings (manual edits after script)

These modifications were required by hand after running the script.
In some cases, the file names did not match patterns. In others,
the format of the file did not match any common patterns.

  • Property mode set to 100644
File size: 9.1 KB
Line 
1RTEMS was developed by On-Line Applications Research (OAR) under
2contract to the U.S. Army Missile Command.  Other than the
3contributions listed in this document, all code and documentation
4was developed by OAR for the Army.
5
6The RTEMS project would like to thank those who have made
7contributions to the project.  Together we make RTEMS a
8much better product.
9
10The following persons/organizations have made contributions:
11
12+ Dr. Mikhail (Misha) Savitski (mikhail.savitski@styrex.se) of the EISCAT
13  Scientific Association submitted the BSP and other miscellaneous support
14  for the Motorola MVME162 (M68040LC CPU) VMEbus single board computer.
15
16+ Greg Allen of Division Inc. of Chapel Hill, NC for
17  porting RTEMS to HP-UX.  This port treats a UNIX computer as simply
18  another RTEMS target processor.  This port can be used to develop
19  and test code which will ultimately run on the embedded platform.
20
21+ Doug McBride (mcbride@rodin.colorado.edu) of the Colorado Space Grant
22  College at the University of Colorado at Boulder submitted the BSP
23  for the Motorola IDP board (M68EC040 CPU) single board computer.  The
24  BSP leverages heavily off of the existing RTEMS BSP framework, the
25  examples in the back of the IDP user's manual, and the libgloss example
26  support for the IDP board from the newlib/libgloss distribution.
27
28+ David Glessner (dwg@glenqcy.glenayre.com) of Glenayre Electronics
29  submitted the support for the Motorola MC68302 CPU.  This included
30  the "gen68302" BSP which uses the on-chip peripherals on the MC68302
31  as well as the modifications to the m68k dependent executive code to
32  support m68k family members based on the mc68000 core.
33
34+ Bryce Cogswell (cogswell@cs.uoregon.edu) submitted the support for MS-DOS
35  as a development environment as well as djgpp/go32 as a target environment.
36
37+ Andy Bray (andy@chaos.org.uk) of I-CUBED Ltd. in Cambridge U.K.
38  for porting RTEMS to the PowerPC.  This effort included support for the
39  IBM 403 as well as the Motorola 601, 603, and 604 variants.  A special
40  thanks to Dom Latter (dom@i-cubed.demon.co.uk) for being an RTEMS
41  evangelist and promoting the use of RTEMS both at I-CUBED Ltd. as well 
42  as within the Internet community as a whole.
43
44+ John S. Gwynne (jsg@coulomb.eng.ohio-state.edu) of Ohio State University
45  submitted the support for the Motorola MC68332 CPU as well as completing
46  the support for CPUs based on the MC68000 core.  Although the BSPs for
47  automotive electronic fuel injection (EFI) control he submitted have now
48  been removed, they formed the foundation for the mrm332 BSP which is still
49  in the tree.
50
51+ The European Space Agency for sponsoring On-Line Applications Research
52  to port RTEMS to the SPARC V7 architecture for use with their ERC32
53  radiation-hardened CPU.  Jiri Gaisler (jgais@wd.estec.esa.nl) deserves
54  special thanks for championing this port within the ESA was well as
55  for developing and supporting the SPARC Instruction Simulator used to
56  develop and test this port.
57
58+ Eric Norum (eric@skatter.usask.ca) of the Saskatchewan Accelerator
59  Laboratory submitted the support for the Motorola MC68360 CPU
60  including the `gen68360' BSP.
61
62+ Dominique le Campion (Dominique.LECAMPION@enst-bretagne.fr), for
63  Telecom Bretagne and T.N.I. (Brest, France) submitted the BSP for
64  the Motorola MVME147 board (68030 CPU + 68881 FPU) and the MVME147s
65  variant of this board.
66
67+ Craig Lebakken (lebakken@minn.net) and Derrick Ostertag
68  (ostertag@transition.com) of Transition Networks of Eden Prairie, MN
69  for porting RTEMS to the MIPS and AMD 29K architectures.  This submission
70  includes complete support for the R4650 as well as partial support
71  for the R4600.
72
73+ Erik Ivanenko (ccms@utcc.utoronto.ca) of the University of Toronto
74  for submitting the i386ex bsp.
75
76+ Jiri Gaisler (jgais@wd.estec.esa.nl) converted RTEMS to using GNU
77  autoconf.  This effort is greatly appreciated.
78
79+ Eric Norum (eric@skatter.usask.ca) of the Saskatchewan Accelerator
80  Laboratory submitted a BSP for the m68360 when operating in companion
81  mode with a m68040 and a port of the Motorola MC68040 Floating Point
82  Support Package (FPSP) to RTEMS.
83
84+ Eric Norum (eric@skatter.usask.ca) of the Saskatchewan Accelerator
85  Laboratory submitted a port of the KA9Q TCP/IP stack to RTEMS as
86  well as a network device driver for the gen68360 BSP.  To address
87  performance issues and licensing concerns, Eric followed this up
88  by replacing the KA9Q TCP/IP stack with a port of the FreeBSD stack.
89
90+ Chris Johns (cjohns@plessey.com.au) submitted the ods68302 BSP which
91  offers easier configuration than its counterpart gen68302.  Chris
92  also submitted the RTEMS++ C++ class library and test code for
93  that library.
94
95+ Katsutoshi Shibuya (shibuya@mxb.meshnet.or.jp) of BU-Denken Co., Ltd.
96  (Sapporo, Japan) submitted the extended console driver for the
97  MVME162LX BSP and the POSIX tcsetattr() and tcgetattr() routines.
98  This device driver supports four serial ports, cooked IO, and
99  provides a portable base for Zilog 8530 based console drivers.
100
101+ Eric Norum (eric@skatter.usask.ca) and Katsutoshi Shibuya
102  (shibuya@mxb.meshnet.or.jp) jointly developed the termios support.
103
104+ Ralf Corsepius (corsepiu@faw.uni-ulm.de) of the Research Institute for
105  Applied Knowledge Processing at the University of Ulm (FAW), Germany,
106  for numerous enhancements to the RTEMS autoconf support as well as
107  for the Hitachi SH port.  His contributions are too many to list but
108  also include work on RPMs for RTEMS tools.
109
110+ Dario Alcocer <alcocer@connectnet.com> submitted a port of the
111  RTEMS port to FreeBSD.
112
113+ David Fiddes <D.J.Fiddes@hw.ac.uk>, Rod Barman (rodb@ptgrey.com) and
114  Stewart Kingdon (kingdon@ptgrey.com) submitted Motorola ColdFire
115  support.  This work was supported in part by Real World Interface, Inc.
116
117+ Geoffroy Montel (g_montel@yahoo.com), for CNET/DSM (Rennes, France),
118  submitted the BSP for Motorola 68340/68349 based boards.
119
120+ Thomas Doerfler (td@imd.m.isar.de) of IMD in
121  Puchheim,Germany submitted some improvements to the PPC403
122  support and added the helas403 BSP.
123
124+ Jay Monkman (jmonkman@frasca.com) of Frasca International, Inc
125  submitted the support for the Motorola MPC860 CPU including the
126  'eth_comm' BSP
127
128+ Charles Gauthier <Charles.Gauthier@iit.nrc.ca> of the Institute for
129  Information Technology for the National Research Council of Canada
130  submitted the Motorola MVME167 BSP.
131
132+ Tony Ambardar (tonya@ece.ubc.ca) at the University of British Columbia
133  ported RTEMS to the TS-1325 embedded PC from Technologic Systems
134  (http://www.t-systems.com), and provided patches to enable software
135  floating-point emulation for x86 targets.
136
137+ Jay Kulpinski (jskulpin@eng01.gdds.com) of General Dynamics Defense
138  Systems (Pittsfield, MA) submitted a board support package for the
139  Motorola MVME230x PowerPC family, borrowing from the PSIM and MPC750
140  BSPs.  This includes support for the Raven ASIC, DEC21140 ethernet,
141  16550 serial port, and MK48T59 NVRAM.
142
143+ Eric Valette <valette@crf.canon.fr> and Emmanuel Raguet <raguet@crf.canon.fr>
144  of Canon CRF - Communication Dept for numerous submissions including
145  remote debugging on the i386 and PowerPC, port of RPC, port of the
146  GoAhead web server, port of RTEMS to the ARM architecture,
147  BSP for the Motorola MCP750 PowerPC board, and numerous improvements
148  to the i386 and PowerPC ports of RTEMS including a new enhanced
149  interrupt management API that reduces interrupt latency while making
150  it easier to support external interrupt controllers.
151
152+ Joel Sherrill <joel@OARcorp.com> for the BSPs that work with
153  numerous simulators including psim, c4xsim, h8sim, armulator,
154  sim68000, and simcpu32.  Most of these BSPs work with instruction
155  set simulators in gdb.
156
157+ Darlene Stewart <Darlene.Stewart@nrc.ca> and Charles Gauthier
158  <Charles.Gauthier@nrc.ca> of the Institute for Information Technology
159  for the National Research Council of Canada submitted the Motorola
160  MBX8XX BSP and consolidated libcpu support for the MPC860 and MPC821
161  into MPC8XX.
162
163+ John Cotton <jcotton@ualberta.ca> and Charles Gauthier
164  <Charles.Gauthier@nrc.ca> of the Institute for Information
165  Technology for the National Research Council of Canada
166  submitted the RTEMS Cache Manager.
167
168+ Philip Quaife <philip@qs.co.nz> of Q Solutions ported
169  RTEMS to the Hitachi H8300H.  This effort was sponsored by
170  Comnet Technologies Ltd.
171
172+ Joel Sherrill <joel@OARcorp.com> and Jennifer Averett <jennifer@OARcorp.com>
173  for the Texas Instruments C3x/C4x port and c4xsim BSP that works
174  with the C3x/C4X instruction set simulator in gdb.
175
176Finally, the RTEMS project would like to thank those who have contributed
177to the other free software efforts which RTEMS utilizes.  The primary RTEMS
178development environment is from the Free Software Foundation (the GNU
179project).  The "newlib" C library was put together by Cygnus and is
180a collaboration of the efforts of numerous individuals and organizations.
181
182We would like to see your name here.  BSPs and ports are always welcome.
183Useful libraries which support RTEMS applications are also an important
184part of providing a strong foundation for the development of real-time
185embedded applications and are welcome as submission.
186
Note: See TracBrowser for help on using the repository browser.