Changes between Version 10 and Version 11 of fbf_device_api


Ignore:
Timestamp:
Jan 22, 2020, 6:29:24 PM (4 years ago)
Author:
alain
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • fbf_device_api

    v10 v11  
    5151This blocking function implements the ''fbf_move_window()'' sys-call. It moves a window identified by the <wid> argument to a new position in the FBF, defined by the <l_min> and <p_min> arguments (FBF coordinates). It can be called by any thread running in any cluster.
    5252
    53 '''5) dev_fbf_resize_window( uint32_t wid, uint32_t width, uint32_t height )'''
     53'''5) error_t  dev_fbf_resize_window( uint32_t wid, uint32_t width, uint32_t height )'''
    5454
    5555This blocking function implements the ''fbf_resize_window()'' sys-call. It changes the <width> and <height> of a window identified by the <wid> argument. It updates the size of the associated vseg, but does not change the vseg "base". When the new window buffer is larger than the existing one, this buffer is 0 filled. It can be called by any thread running in any cluster.
    5656
    57 '''6) dev_fbf_delete_window( uint32_t wid )'''
     57'''6) error_t  dev_fbf_delete_window( uint32_t wid )'''
    5858
    5959This function implements the ''fbf_delete_window()'' sys-call to delete a FBF window identified by the <wid> argument. It releases all memory allocated for the window buffer and for the window descriptor. It can be called by any thread running in any cluster.
    6060
    61 '''7) dev_fbf_move_data( bool_t    is_write, void * user_buffer, uint32_t npixels, uint32_t offset )'''
     61'''7) error_t  dev_fbf_move_data( bool_t is_write, void * user_buffer, uint32_t npixels, uint32_t offset )'''
    6262
    6363This function is deprecated. It implements the deprecated ''fbf_read()'' and ''fbf_write()'' sys-calls. This function allows an user application to directly access the Frame Buffer, without using any intermediate window. It calls directly the driver to synchronously move <npixels> between an user <buffer> and the FBF, starting at a given <offset> in the FBF. The transfer direction is defined by the <is_write> argument.