source: rtems/c/ACKNOWLEDGEMENTS @ 0724887f

4.104.114.84.95
Last change on this file since 0724887f was 78a9564, checked in by Joel Sherrill <joel.sherrill@…>, on 01/07/04 at 21:17:46

2004-01-07 Joel Sherrill <joel@…>

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