Changes between Version 11 and Version 12 of peripherals_drivers

Timestamp:

Sep 17, 2015, 9:17:01 AM (10 years ago)

Author:

alain

Comment:

--

peripherals_drivers

@@ -3 +3 @@
 [[PageOutline]]
 
-The GIET_VM supports two types of peripheral components: '''External peripherals''' are located in one single cluster (called ''cluster_io'', and identified by the ''X_IO,Y_IO'' variables). '''Internal peripherals''' (such as DMA, XCU, or MMC) are replicated in all clusters.
+The GIET_VM supports two types of peripheral components: '''External peripherals''' are located in one single cluster (called ''cluster_io'', and identified by the ''X_IO,Y_IO'' variables). '''Internal peripherals''' (such as XCU, or MMC) are replicated in all clusters.
 
 Each driver xxx_driver define two low-level functions ''_xxx_get_register()'' and ''_xxx_set_register()''
@@ -14 +14 @@
 The X_IO, Y_IO, and PERI_CLUSTER_INCREMENT variables must be defined in the ''hard_config.h" file.
 
-Some peripherals (TTY, TIM, NIC, CMA, HBA) are multi-channels peripherals: Each channel provide an independent set of addressable registers, and each channel can be seen as an independent hardware resource. For  multi-channels peripherals, the GIET_VM allows an user application to allocate a ''private'' peripheral channel, that cannot be used by other applications.  The corresponding channel index is stored in the calling task context. For some peripherals (such as TTY or TIM), the allocated channel can be shared by all tasks in the same vspace as the calling task.
+Some peripherals (TTY, TIM, NIC, CMA, HBA) are multi-channels peripherals: Each channel provide an independent set of addressable registers, and each channel can be seen as an independent hardware resource. For  multi-channels peripherals, the GIET_VM allows an user application to dynamically allocate a ''private'' peripheral channel, that cannot be used by other applications.  The corresponding channel index is stored in the calling thread context. For some peripherals (such as TTY), the allocated channel can be shared by all threads in the same vspace as the calling thread.
 
  === [wiki:bdv_driver     BDV  (Block Device controller)]