forked from Imagelibrary/rtems
abdeac2a14
PR 1793/doc * .cvsignore, Makefile.am, README, configure.ac, index.html.in, main.am, project.am, ada_user/.cvsignore, ada_user/ada_user.texi, ada_user/example.texi, bsp_howto/.cvsignore, bsp_howto/bsp_howto.texi, cpu_supplement/.cvsignore, cpu_supplement/cpu_supplement.texi, cpu_supplement/preface.texi, develenv/.cvsignore, develenv/develenv.texi, develenv/intro.texi, filesystem/.cvsignore, filesystem/filesystem.texi, filesystem/preface.texi, networking/.cvsignore, networking/networking.texi, networking/preface.texi, porting/.cvsignore, porting/porting.texi, porting/preface.texi, posix1003.1/.cvsignore, posix1003.1/posix1003_1.texi, posix_users/.cvsignore, posix_users/posix_users.texi, posix_users/preface.texi, shell/.cvsignore, shell/preface.texi, shell/shell.texi, started/.cvsignore, started/started.texi, user/.cvsignore, user/c_user.texi, user/dirstat.texi, user/example.texi, user/glossary.texi, user/preface.texi: Convert from texi2www to texi2html. * texi2html_init.in: New file. * rtems_footer.html.in, rtems_header.html.in: Removed.
41 lines
1.3 KiB
Plaintext
41 lines
1.3 KiB
Plaintext
@c
|
|
@c COPYRIGHT (c) 1989-2011.
|
|
@c On-Line Applications Research Corporation (OAR).
|
|
@c All rights reserved.
|
|
@c
|
|
@c $Id$
|
|
@c
|
|
|
|
@node Preface, Development Tools, Top, Top
|
|
@unnumbered Preface
|
|
|
|
The purpose of this manual is to provide a roadmap to those people porting
|
|
RTEMS to a new CPU family. This process includes a variety of activities
|
|
including the following:
|
|
|
|
@itemize @bullet
|
|
|
|
@item targeting the GNU development tools
|
|
|
|
@item porting the RTEMS executive code
|
|
|
|
@item developing a Board Support Package
|
|
|
|
@item writing an RTEMS CPU Supplement manual for the completed port.
|
|
|
|
@end itemize
|
|
|
|
This document focuses on the process of actually porting the RTEMS
|
|
executive code proper. Each of the data structures, routines, and macro
|
|
definitions required of a port of RTEMS is described in this document.
|
|
|
|
Porting any operating system, including RTEMS, requires knowledge of the
|
|
operating system, target CPU architecture, and debug environment. It is
|
|
very desirable to have a CPU simulator or hardware emulator when debugging
|
|
the port. This manual assumes that the user is familiar with building and
|
|
using RTEMS, the C programming language, and the target CPU architecture.
|
|
It is desirable to be familiar with the assembly language for the target
|
|
CPU family but since only a limited amount of assembly is required to port
|
|
RTEMS.
|
|
|