diff options
| author | Stephane Marchesin <stephane.marchesin@gmail.com> | 2010-12-20 00:33:35 -0800 |
|---|---|---|
| committer | Stephane Marchesin <stephane.marchesin@gmail.com> | 2010-12-20 00:33:35 -0800 |
| commit | 9cd1f53e6d553cfaea3f7e0563aaa2bfb9e4f176 (patch) | |
| tree | 52a1b0d11e875a8af03c999ffac4b89783f117a5 | |
| parent | 1b0cc8a29f1069b9e4df7c6b74a66e5fff80e94b (diff) | |
Small changes.
| -rw-r--r-- | linuxgraphicsdrivers.lyx | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/linuxgraphicsdrivers.lyx b/linuxgraphicsdrivers.lyx index bbf3360..d8f3900 100644 --- a/linuxgraphicsdrivers.lyx +++ b/linuxgraphicsdrivers.lyx @@ -4499,8 +4499,9 @@ name "cha:Framebuffer-Drivers" Framebuffer drivers are the simplest form of graphics drivers under Linux. Kernel modesetting DRM drivers are still a relevant option if the only thing you are after is a basic two-dimensional display. - Furthermore, when implementing framebuffer acceleration on top of a kernel - modesetting DRM driver, the same callbacks need to be filled. + It is also useful to know how framebuffer drivers work when implementing + framebuffer acceleration on top of a kernel modesetting DRM driver, as + the acceleration callbacks are the same. A framebuffer driver implements little functionality, and is therefore extremely easy to create. Such a driver is especially interesting for embedded systems, where memory |