Changes between Version 2 and Version 3 of bdv_driver

Timestamp:

Oct 7, 2014, 1:55:49 PM (10 years ago)

Author:

alain

Comment:

--

bdv_driver

@@ -8 +8 @@
  * In '''BOOT''' mode, these functions use a polling policy on the BDV STATUS register to detect transfer completion, as interrupts are not activated. This mode is used by the boot code to load the map.bin file into memory (before MMU activation), or to load the .elf files (after MMU activation). 
  * In '''KERNEL''' mode, these functions use a descheduling strategy: The ISR executed when transfer completes should restart the calling task. There is no checking of user access right to the memory buffer. This mode must be used, for an ''open'' system call.
- * In '''USER''' mode, these functions use a descheduling strategy: The ISR executed when transfer completes should restart the calling task. The user access right to the memory buffer must be checked.
-This mode must be used for a ''read'' or ''write' system call.
+ * In '''USER''' mode, these functions use a descheduling strategy: The ISR executed when transfer completes should restart the calling task. The user access right to the memory buffer must be checked. This mode must be used for a ''read'' or ''write'' system call.
 
 The BDV component is single channel, but can be used by several programs running in parallel, as the _bdv_lock variable guaranties exclusive access to the device.  The _bdv_read() and _bdv_write() functions use atomic LL/SC to get the lock.