mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-03-11 04:50:35 +01:00
docs/xlib: Drop docs about long-dead X features.
Nobody's doing 8-bit color-indexed rendering, and the overlay planes referenced here are not anything that X drivers support these days, and they were never ported to gallium. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/39741>
This commit is contained in:
parent
cbec12627b
commit
cf445c1995
1 changed files with 0 additions and 26 deletions
|
|
@ -64,32 +64,6 @@ blending will require a round-trip message for pixel readback.)
|
|||
Experiment with the MESA_BACK_BUFFER variable to see which is faster for
|
||||
your application.
|
||||
|
||||
Colormaps
|
||||
---------
|
||||
|
||||
When using Mesa directly or with GLX, it's up to the application writer
|
||||
to create a window with an appropriate colormap. The GLUT toolkit tries
|
||||
to minimize colormap *flashing* by sharing colormaps when possible.
|
||||
Specifically, if the visual and depth of the window matches that of the
|
||||
root window, the root window's colormap will be shared by the Mesa
|
||||
window. Otherwise, a new, private colormap will be allocated.
|
||||
|
||||
When sharing the root colormap, Mesa may be unable to allocate the
|
||||
colors it needs, resulting in poor color quality. This can happen when a
|
||||
large number of colorcells in the root colormap are already allocated.
|
||||
|
||||
Overlay Planes
|
||||
--------------
|
||||
|
||||
Hardware overlay planes are supported by the Xlib driver. To determine
|
||||
if your X server has overlay support you can test for the
|
||||
SERVER_OVERLAY_VISUALS property:
|
||||
|
||||
.. code-block:: sh
|
||||
|
||||
xprop -root | grep SERVER_OVERLAY_VISUALS
|
||||
|
||||
|
||||
Extensions
|
||||
----------
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue