From 33cd2d43a18851aafdcb6bbdeebab679d8ab1c86 Mon Sep 17 00:00:00 2001 From: Joel Sherrill Date: Wed, 6 Oct 1999 19:36:28 +0000 Subject: New manual. First version to CVS. Just starting to see if it builds. --- doc/porting/preface.t | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+) create mode 100644 doc/porting/preface.t (limited to 'doc/porting/preface.t') diff --git a/doc/porting/preface.t b/doc/porting/preface.t new file mode 100644 index 0000000000..b180a63b4c --- /dev/null +++ b/doc/porting/preface.t @@ -0,0 +1,32 @@ + +@chapter 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. + -- cgit v1.2.3