xserver/hw/kdrive/fbdev/Xfbdev.man
stefan11111 de16c2dd4d kdrive: Move glamor and linux info from the Xfbdev man page to the Xkdrive man page
Signed-off-by: stefan11111 <stefan11111github@gmail.com>
2026-09-16 16:22:36 +02:00

88 lines
3.4 KiB
Groff

.\" $RCSId: xc/programs/Xserver/hw/kdrive/fbdev/Xfbdev.man,v 1.4 2001/01/27 18:20:40 dawes Exp $
.\"
.TH Xfbdev 1 __vendorversion__
.SH NAME
Xfbdev \- Linux framebuffer device tiny X server
.SH SYNOPSIS
.B Xfbdev
.RI [ :display ]
.RI [ option ...]
.SH DESCRIPTION
.B Xfbdev
is a generic X server for Linux.
.B Xfbdev
doesn't know about any particular hardware, and uses the framebuffer
provided by the Linux framebuffer device.
.SH OPTIONS
.B Xfbdev
accepts the common options of the Xkdrive family of servers. Please
see Xkdrive(@appmansuffix@).
.B Xfbdev
also accepts the following additional options:
.TP 8
.B -fb "</dev/fbxx>"
sets the framebuffer device path the X server will use.
.TP 8
.B -noshadow
disables the ShadowFB layer on supported hw, may slightly increase performance.
May also lead to flickering.
.SH CONFIGURATION
.
Like all kdrive X servers,
.B Xfbdev
doesn't read any configuration file.
Instead, all configuration is done via command-line arguments.
.B Xfbdev
is intended to provide a reasonable configuration out-of-the-box, with no special configuration.
Simply running
.B xinit -- /path/to/Xfbdev
should provide a default configuration that is able to provide a usable display.
This default configuration is rather simplistic, with the aim of working
almost anywhere, while sacrificing performance.
For regular use, a shell script or similar can be created to invoke xinit and pass all the necessary command-line arguments.
In the most general form, the configuration of
.B Xfbdev
looks like this:
.B xinit -- /path/to/Xfbdev [server_args] [screen_0_args] -screen [geom] [screen_1_args] -screen [geom] ... [screen_n_args] -screen [geom] [screen_n_args]
Arguments whose effect is intended to affect the entire X server instead of a particular screen (e.g. +xinerama) can be added anywhere,
but they are usually added before the arguments of the first screen.
If a single X11 screen is desired, with no special geometry,
.B Xfbdev
supports using an implicit first screen, like so:
.B xinit -- /path/to/Xfbdev [server_args] [screen_args]
Below are listed some example configurations, intended to serve as a guide for configuring
.B Xfbdev.
A single X11 screen with DRI3 running on a different card than the framebuffer, with an explicit glvendor and with only OpenGL ES contexts allowed:
.B xinit -- /usr/bin/Xfbdev :1 -fb /dev/fb0 -glvendor nvidia -dri /dev/dri/card1 -force-es
Two X11 screens with DRI3 support, with the first screen on the left, the second screen on the right:
.B xinit -- /usr/bin/Xfbdev -dri /dev/dri/card1 -fb /dev/fb0 -screen 1920x1080 -fb /dev/fb1 -dri /dev/dri/card1 -screen 1920x1080
Two X11 screens with DRI3 support, with the first screen on the left, the second screen on the right, using xinerama:
.B xinit -- /usr/bin/Xfbdev +xinerama -dri /dev/dri/card1 -fb /dev/fb0 -screen 1920x1080 -fb /dev/fb1 -dri /dev/dri/card1 -screen 1920x1080
Two X11 screens, the first one below the second one:
.B xinit -- /usr/bin/Xfbdev -fb /dev/fb0 -origin 0,1080 -screen 1920x1080 -fb /dev/fb1 -origin 0,0 -screen 1920x1080
.SH KEYBOARD
.B Xfbdev
supports the common special key combinations of the Xkdrive family of servers. Please
see Xkdrive(@appmansuffix@).
.SH SEE ALSO
X(@miscmansuffix@), Xserver(@appmansuffix@), Xkdrive(@appmansuffix@), xdm(@appmansuffix@), xinit(@appmansuffix@).
.SH AUTHORS
The
.B Xfbdev
server was written by Keith Packard.
HW acceleration support was later added by stefan11111.