source: rtems/doc/supplements/mips/memmodel.t @ 891d63bd
Last change on this file since 891d63bd was 891d63bd, checked in by Joel Sherrill <joel.sherrill@…>, on 02/14/02 at 22:14:59

2002-02-04 Joel Sherrill <joel@…>

  • bsp.t, BSP_TIMES, callconv.t, ChangeLog?, cpumodel.t, cputable.t, fatalerr.t, intr_NOTIMES.t,, memmodel.t, mips.texi, preface.texi, stamp-vti, timeBSP.t, version.texi: New files.
  • Property mode set to 100644
File size: 1.4 KB
2@c  COPYRIGHT (c) 1988-2002.
3@c  On-Line Applications Research Corporation (OAR).
4@c  All rights reserved.
6@c  $Id$
9@chapter Memory Model
11@section Introduction
13A processor may support any combination of memory
14models ranging from pure physical addressing to complex demand
15paged virtual memory systems.  RTEMS supports a flat memory
16model which ranges contiguously over the processor's allowable
17address space.  RTEMS does not support segmentation or virtual
18memory of any kind.  The appropriate memory model for RTEMS
19provided by the targeted processor and related characteristics
20of that model are described in this chapter.
22@section Flat Memory Model
24The XXX family supports a flat 32-bit address
25space with addresses ranging from 0x00000000 to 0xFFFFFFFF (4
26gigabytes).  Each address is represented by a 32-bit value and
27is byte addressable.  The address may be used to reference a
28single byte, word (2-bytes), or long word (4 bytes).  Memory
29accesses within this address space are performed in big endian
30fashion by the processors in this family.
32Some of the XXX family members such as the
33XXX, XXX, and XXX support virtual memory and
34segmentation.  The XXX requires external hardware support
35such as the XXX Paged Memory Management Unit coprocessor
36which is typically used to perform address translations for
37these systems.  RTEMS does not support virtual memory or
38segmentation on any of the XXX family members.
Note: See TracBrowser for help on using the repository browser.