summaryrefslogtreecommitdiffstats
path: root/docs/glfbdev-driver.html
blob: b49950eb9e1bb144b40329df62df26f182ca29bc (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
<HTML>

<TITLE>Mesa glFBDev Driver</TITLE>

<link rel="stylesheet" type="text/css" href="mesa.css"></head>

<BODY>

<center><H1>Mesa glFBDev Driver</H1></center>


<H1>1. Introduction</H1>

<p>
The GLFBDev driver interface allows one to do OpenGL rendering into a
framebuffer managed with the Linux's fbdev interface.
</p>

<p>
Basically, the programmer uses the fbdev functions to initialize the
graphics hardware and setup the framebuffer.
Then, using a calls to Mesa's glFBDev API functions, one can render
into the framebuffer with the OpenGL API functions.
</p>

<p>
Note, only software rendering is supported; there is no hardware
acceleration.
</p>


<p>
The GL/glfbdev.h header file defines the glFBDev interface.
</p>

<p>
The progs/fbdev/glfbdevtest.c demonstrates how to use the glFBDev interface.
</p>

<p>
For more information about fbdev, see the
<a href="http://www.tldp.org/HOWTO/Framebuffer-HOWTO.html" target="_parent">
Framebuffer Howto</a>
</p>


<h1>2. Compilation</h1>

<p>
To compile Mesa with support for the glFBDev interface:
<pre>
   XXX todo
</pre>

<p>
When compilation is finished look in progs/glfbdev/ for the glfbdevtest demo.
</p>

</p>
xxx todo
</p>


<h1>3. Compiling and linking glFBDev programs</h1>

<p>
xxx todo
</p>



<h1>4. Running glFBDev programs</h1>

<p>
First, you need to have a working fbdev environment.
See the
<a href="http://www.tldp.org/HOWTO/Framebuffer-HOWTO.html" target="_parent">
Framebuffer Howto</a> for information.
</p>

<p>
Programs must be run with root permission.
</p>

</p>



</body>
</html>