Changes between Version 11 and Version 12 of DsxvmMappingInfoStructure

Timestamp:

Sep 7, 2012, 9:48:49 AM (12 years ago)

Author:

karaoui

Comment:

--

DsxvmMappingInfoStructure

@@ -124 +124 @@
  * `name`: the name of the virtual object. This is used to obtain the virtual base address of the vobj: this name is a parameter of the vobj_get_vbase syscall along with the vspace name. Two vobj elements can't have the same name inside a vspace, even if they are in different vseg elements.
  * `type`: type of the virtual object. It can be one of the following:
-   * `ELF`: describes an elf section. The system has to load the elf described by the binpath in this segment.
+   * `ELF`: describes an elf section. The system has to load the elf described by the binpath in this segment. This type has two constraint :
+      * He must be alone in a virtual segment (vseg)
+      * The vbase of the vseg must be equal to the one defined in the ldscript
    * `PTAB`: memory space reservation for the page table. Each vspace must have one vobj of this type. The system will have to initialize the page tables with the information contained in this file.
    * `PERI`: type of vseg used for peripheral mapping. No particular action is performed by the operating system on this type of segment.
@@ -165 +167 @@
  * `startid`: indicates the index of the function to execute in the task function entry table of the corresponding vspace.
  * `usefbdma`: (optional) if set (with value 1), indicates that the task uses a frame buffer with dma accesses (`fb_write` function).
-