Changes between Version 6 and Version 7 of txt_device_api

Timestamp:

Jan 22, 2020, 3:00:40 PM (5 years ago)

Author:

alain

Comment:

--

txt_device_api

@@ -50 +50 @@
 Note : According to the scheduler policy, the DEV thread has an higher priority than any user thread, but it is not selected when the associated waiting queue is empty.
 
-'''C.2) Synchronous operations'''
+'''C.2) Synchronous operation'''
 
 * The '''dev_txt_sync_write( char * buffer , uint32_t count  )''' function moves  <count> characters from the the kernel buffer identified by the <buffer> pointer, to the kernel TXT0 terminal.
 
-Almost-mkh uses this operation to synchronously display debug or log information on the kernel terminal using the print()
-kernel function, and we want to avoid any interference with another TXT I/O operation. We don't want to use the TXT device waiting queue, the associated server thread, and the ''txt_command_t'' structures used by the ''txt_driver_cmd()'' function. Therefore, this function directly call the ''txt_driver_aux()'' function, and the txt_sync_args_s structure for the arguments.
+Almost-mkh uses this operation to synchronously display debug or log messages on the kernel terminal, using the printk() kernel function, and we want to avoid any interference with another TXT I/O operation. We don't want to use the TXT device waiting queue, the associated server thread, and the ''txt_command_t'' structures used by the ''txt_driver_cmd()'' function. Therefore, this function directly call the ''txt_driver_aux()'' function, and the txt_sync_args_s structure for the arguments.
  
 == __D) The "driver" API__ ==