Changes between Version 12 and Version 13 of peripherals_drivers

Timestamp:

Sep 17, 2015, 1:32:48 PM (9 years ago)

Author:

alain

Comment:

--

peripherals_drivers

@@ -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 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.
+== Shared and private peripherals ==
+
+Some peripherals (such as BDV, SDC, FBF) deliver an unique service, and are shared by all applications under the
+kernel supervision.
+
+Some peripherals (TTY, TIM, NIC, CMA) 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 TIM, the private timer index is hidden, and can only be used by the thread making the allocation.
+ * For TTY, the private channel index is hidden, but the the thread making the allocation can ask a totally private terminal, or a partially shared terminal usable by all threads in the same vspace.
+ * For NIC, the channel index is returned to the thread making allocation, and can be used by all threads in the same vspace.  
 
  === [wiki:bdv_driver     BDV  (Block Device controller)]