Changes between Version 1 and Version 2 of DsxMapping

Timestamp:

Mar 18, 2008, 5:21:18 PM (17 years ago)

Author:

Nicolas Pouillon

Comment:

--

DsxMapping

@@ -24 +24 @@
      A memory Segment to put the task's description in. This description won't be written to.
      Segment may be read-only memory.
-   * `status`:
-     A memory Segment to put dynamic status on. This must be uncached in order to be
-     able to use inter-cpu communications.
- * Optional arguments:
-   * `code`:
-     A memory segment to copy task code in. This won't be written to. If not specified,
-     code will be placed in global code segment, specified when mapping OS objects.
  * Example:
 {{{
 mapper.map( "cons0",
-            run = mapper.hard.processor,
+            run   = mapper.hard.processor,
             stack = mapper.hard.cram0,
-            desc = mapper.hard.cram0,
-            status = mapper.hard.uram0,
-            code = mapper.hard.cram0)
+            desc  = mapper.hard.cram0)
 }}}
 
@@ -53 +44 @@
 mapper.map( "cons0",
             vci = mapper.hard.vgmn)
+}}}
+
+= Memspaces =
+
+ * Mandatory arguments:
+   * `desc`:
+     A memory Segment to put the memspace's description in. This description won't be written to.
+     Segment may be read-only memory.
+   * `buffer`:
+     A memory Segment to put data in.
+ * Example:
+{{{
+mapper.map( "memsp",
+            desc   = mapper.hard.cram1,
+            buffer = mapper.hard.cram1)
+}}}
+
+= Locks =
+
+ * Mandatory arguments:
+   * `lock`:
+     A memory Segment to put the lock in.
+ * Example:
+{{{
+mapper.map( "lock0",
+            lock = mapper.hard.cram1)
 }}}
 
@@ -73 +90 @@
             desc    = mapper.hard.cram1)
 }}}
-
 = Processor =