source: rtems/doc/supplements/i960/memmodel.t @ 1e524995

4.104.114.84.95
Last change on this file since 1e524995 was 1e524995, checked in by Joel Sherrill <joel.sherrill@…>, on 02/06/98 at 14:14:30

Updated copyrights

  • Property mode set to 100644
File size: 1.9 KB
Line 
1@c
2@c  COPYRIGHT (c) 1988-1998.
3@c  On-Line Applications Research Corporation (OAR).
4@c  All rights reserved.
5@c
6@c  $Id$
7@c
8
9@ifinfo
10@node Memory Model, Memory Model Introduction, Calling Conventions Leaf Procedures, Top
11@end ifinfo
12@chapter Memory Model
13@ifinfo
14@menu
15* Memory Model Introduction::
16* Memory Model Flat Memory Model::
17@end menu
18@end ifinfo
19
20@ifinfo
21@node Memory Model Introduction, Memory Model Flat Memory Model, Memory Model, Memory Model
22@end ifinfo
23@section Introduction
24
25A processor may support any combination of memory
26models ranging from pure physical addressing to complex demand
27paged virtual memory systems.  RTEMS supports a flat memory
28model which ranges contiguously over the processor's allowable
29address space.  RTEMS does not support segmentation or virtual
30memory of any kind.  The appropriate memory model for RTEMS
31provided by the targeted processor and related characteristics
32of that model are described in this chapter.
33
34@ifinfo
35@node Memory Model Flat Memory Model, Interrupt Processing, Memory Model Introduction, Memory Model
36@end ifinfo
37@section Flat Memory Model
38
39The i960CA supports a flat 32-bit address space with
40addresses ranging from 0x00000000 to 0xFFFFFFFF (4 gigabytes).
41Although the i960CA reserves portions of this address space,
42application code and data may be placed in any non-reserved
43areas.  Each address is represented by a 32-bit value and is
44byte addressable.  The address may be used to reference a single
45byte, half-word (2-bytes), word (4 bytes), double-word (8
46bytes), triple-word (12 bytes) or quad-word (16 bytes).  The
47i960CA does not support virtual memory or segmentation.
48
49The i960CA allows the memory space to be partitioned
50into sixteen regions which may be configured individually as big
51or little endian.  RTEMS assumes that the memory regions in
52which its code, data, and the RTEMS Workspace reside are
53configured as little endian.
54
55
Note: See TracBrowser for help on using the repository browser.