diff options
| author | Stéphane Marchesin <marcheu@chromium.org> | 2012-09-02 21:56:00 -0700 |
|---|---|---|
| committer | Stéphane Marchesin <marcheu@chromium.org> | 2012-09-02 21:56:00 -0700 |
| commit | 9e27d83954a7f226fc5d04901e8c3976c9cf1a8d (patch) | |
| tree | 41a2e880cab0ae3f6e42c70045c6e332b2348d09 | |
| parent | d003af7799d6dd7232b17708517e448f3cfffce6 (diff) | |
Small changes.
| -rw-r--r-- | linuxgraphicsdrivers.lyx | 34 |
1 files changed, 30 insertions, 4 deletions
diff --git a/linuxgraphicsdrivers.lyx b/linuxgraphicsdrivers.lyx index b6e6f4d..2edadac 100644 --- a/linuxgraphicsdrivers.lyx +++ b/linuxgraphicsdrivers.lyx @@ -4690,8 +4690,8 @@ Framebuffer drivers are the simplest form of graphics drivers under Linux. a video mode and drawing to a linear framebuffer), and the framebuffer drivers are therefore extremely simple and easy to create. Despite their simplicity, framebuffer drivers are still a relevant option - if the only thing you are after is a basic two-dimensional display with no - bells and whistles. + if the only thing you are after is a basic two-dimensional display with + no bells and whistles. It is also useful to know how framebuffer drivers work when implementing framebuffer acceleration for a kernel modesetting DRM driver, as the accelerati on callbacks are the same. @@ -5575,6 +5575,8 @@ To prevent access to arbitrary GPU memory, the command submission ioctl and reject the batch buffer if it isn't. That way it is possible to implement memory protection when the hardware doesn't provide that functionality. + Although there is some overhead for doing command buffer parsing, it is + bearable, and this is how the open source radeon drivers work. \end_layout \begin_layout Standard @@ -5586,9 +5588,33 @@ GEM, TTM \begin_layout Standard \lang english +map/unmap ioctls +\end_layout + +\begin_layout Standard + +\lang english +pwrite +\end_layout + +\begin_layout Standard + +\lang english Share video memory \end_layout +\begin_layout Standard + +\lang english +flink +\end_layout + +\begin_layout Standard + +\lang english +dma_buf +\end_layout + \begin_layout Section \lang english @@ -9001,8 +9027,8 @@ emulate Therefore gallium drivers become smaller and easier to write and to maintain. The same concept is applied to other aspects of the 3D APIs like surface handling; things like mipmap generation, surface copies and pixel format - conversions are all handled in common code and can be shared between - multiple drivers. + conversions are all handled in common code and can be shared between multiple + drivers. \end_layout \begin_layout Standard |