Changes between Version 130 and Version 131 of library_stdio

Timestamp:

Nov 1, 2015, 12:15:40 AM (10 years ago)

Author:

alain

Comment:

--

library_stdio

@@ -410 +410 @@
 
  === 2) void '''giet_fbf_alloc'''() ===
-This blocking function allows the calling thread to get exclusive ownership of the shared FBF peripheral.
+This blocking function allows an application to get exclusive ownership of the shared FBF peripheral.
 It returns only when the lock has been taken.
-All theads in the same space as the calling thread can access concurrently the frame buffer, under the user responsibility.
-This lock is released when the thread completes execution, after a giet_pthread_exit(), or a giet_pthread_kill().
+All threads in the same space as the calling thread can access concurrently the frame buffer, under the user responsibility.
+This lock is released only when when all threads in the application complete execution, after a giet_pthread_exit(), or a giet_pthread_kill().
 
  === 3) void '''giet_fbf_cma_alloc'''( unsigned int nbufs )
-This function allocates a private CMA channel  to the calling thread, and registers the channel index in the thread context. 
+This function allocates a CMA channel  to an application, and registers the channel index in the contexts of all threads that are in the same space as the calling thread. 
 The <nbufs> argument define the total number of chained user buffers. 
 As each user buffer contains one image, the buffer size must be FBUF_X_SIZE * FBUF_Y_SIZE.
@@ -425 +425 @@
  === 4) void '''giet_fbf_cma_init_buf'''( unsigned int index  void* buf_vaddr , void* sts_vaddr ) ===
 This function initializes the chained buffer descriptor for one user buffer identified by the <index> argument.
+The <buf_vaddr> and <sts_vaddr> arguments are pointers on the buffer and on the buffer status. 
 This <index> argument must be smaller than the <nbufs> argument in giet_fbf_cma_alloc() above.
 The set of user buffers will be transferred by the CMA peripheral in the order of increasing indexes.
 This function must be called <nbufs> times, to initialize the <nbufs> chained buffers descriptors. 
 Each user buffer must be large enough to store a complete image, and must be aligned on a 64 bytes boundary.
-The buffer status contain just a Boolean, but it must occupy 64 bytes, and must be aligned on a 64 bytes boundary.
-For a given user buffer, the buffer and the associated status must be in the same cluster.
- * '''index''' : buffer index 
- * '''buf_vaddr''' : virtual address of the user buffer.
- * '''sts_vaddr''' : virtual address of the buffer status.
+The buffer status contain just a Boolean, but it must occupy 64 bytes, and must be aligned on a 64 bytes boundary. For a given user buffer, the buffer and the associated status must be in the same cluster.
 The thread exit if buffers are not aligned, index too large, or buffer and status in different clusters.