[ac7d5ef0] | 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 (mms@eiscathq.irf.se) of the EISCAT Scientific |
---|
| 17 | Association submitted the BSP and other miscellaneous support for the |
---|
| 18 | 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@divnc.com) was assisted in this effort by Joel Sherrill |
---|
| 24 | (jsherril@redstone.army.mil). Tony also deserves a big pat on the |
---|
| 25 | back for contributing significantly to the overall organization |
---|
| 26 | of the development environment and directory structure. RTEMS |
---|
| 27 | is much easier to build 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 | |
---|
[620d699] | 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 | |
---|
[637df35] | 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 | |
---|
[6b45e470] | 50 | + Andy Bray (andy@i-cubed.demon.co.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 | |
---|
[38ffa0c] | 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 | |
---|
[ac7d5ef0] | 67 | Finally, the RTEMS project would like to thank those who have contributed |
---|
| 68 | to the other free software efforts which RTEMS utilizes. The primary RTEMS |
---|
| 69 | development environment is from the Free Software Foundation (the GNU |
---|
| 70 | project). The "newlib" C library was put together by Cygnus and is |
---|
| 71 | a collaboration of the efforts of numerous individuals and organizations. |
---|
| 72 | |
---|
| 73 | We would like to see your name here. BSPs and ports are always welcome. |
---|
| 74 | Useful libraries which support RTEMS applications are also an important |
---|
| 75 | part of providing a strong foundation for the development of real-time |
---|
| 76 | embedded applications and are welcome as submission. |
---|
| 77 | |
---|