Two software architectures for Linux framebuffer Drive framework (not to be continued) "Turn"

This article was reproduced from: http://blog.csdn.net/gqb_driver/article/details/12918547

/************************************************************************************************************** **********************/

Original works, when reproduced, please be sure to indicate the original source of the article in the form of hyperlinks: http://blog.csdn.net/gqb666/article/details/12918547, Author: gqb666
/************************************************************************************************************** **********************/

Work is too busy, led to the brother of the Linux Framebuffer Drive series blog stranded for a period of time, today, the mood to start. In the previous blog, "Linux Framebuffer driver Framework, one of the concept introduction and the principle of LCD hardware," mainly describes the concept of Framebuffer and LCD hardware principles, the text will focus on the Linux Framebuffer Drive framework software architecture, The relationship between the various levels is visualized in the form of block diagram. As shown, see what the Framebuffer software architecture looks like:

Figure 1 Framebuffer device-driven software architecture

The read/write interface provided by the framebuffer frame buffer device to the user state file_operations is actually provided by a specific File_operatins structure object in the Fbmem.c file, and the specific frame buffer device Fb_info The structure's registration, The logoff and the maintenance of its members, especially the implementation of member functions in Fb_ops, are implemented by the corresponding XXXFB.C file, and the member function in Fb_ops will eventually operate the register of the LCD controller.

Next, take Linux 2.6.37 as an example, draw a UML diagram of each structure relationship, and briefly describe the process from application to driver.

In fact, through the block diagram we see the structure, but not only floating on the surface, the meaning of the data structure and the implementation of the function is our main play, OK, let us uncover her mysterious veil, see the essence, the next turn to the Linux Framebuffer Drive framework of the three related core data structure (to be continued).

Two software architectures for Linux framebuffer Drive framework (not to be continued) "Turn"