Integrating Display Classes

This section discusses which steps it takes to port the Display Class to a new system. It will refer to the Display Class example implementation and the Services unit test rgx_blit_test found under:

GPU_PATH/services/display/dc_example/...

GPU _PATH/unittests/services/rogue/external/rgx_blit_test/...

The dc_example implementation shows how a Display Class component implementation could look like and the test is exemplifying how to integrate the Services Display Class client function calls in the rendering workflow of a client application. Usually this client application is a window manager but, in this example, (rgx_blit_test) the rendering application directly makes calls to the Display Class client API.

The dc_example module was designed to work without actual display hardware and just implements the basics to make it work with the Display Class workflow.

Figure 1. Call Graph For Re-Configuration

The above diagram shows a typical function call stack for a reconfiguration call that originates from the window manager; in this case a Services WSEGL implementation. It is based on the diagram in Service Architecture and is the path most calls from the window manager (client application) to the Display Class client interface take.