Difference between revisions of "X11 server"
From ArmadeusWiki
(→Launching) |
(→Launching) |
||
Line 33: | Line 33: | ||
==Launching== | ==Launching== | ||
− | * For example, with a mouse and a keyboard (event0) | + | * For example, with a mouse and a keyboard (event0): |
<pre class="apf"> | <pre class="apf"> | ||
# /usr/bin/X -mouse evdev -retro -keybd evdev,,device=/dev/input/event0 & | # /usr/bin/X -mouse evdev -retro -keybd evdev,,device=/dev/input/event0 & | ||
+ | </pre> | ||
+ | * Or with a touchscreen (event0): | ||
+ | <pre class="apf"> | ||
+ | # /usr/bin/X -retro -mouse tslib,,device=/dev/input/event0 & | ||
</pre> | </pre> | ||
Revision as of 16:44, 7 December 2015
Introduction
Even if using an Xserver in an embedded context is most of the times not a necessity, it could be interesting in some "PDA like" applications, where existing applications reuse is needed. Even if recent embedded systems are capable of running a full Xorg server, in embedded systems we prefer to use the reduced version TinyX/Xfbdev, which is an upper layer of the Linux Framebuffer.
Installing
$ make menuconfig
Target packages ---> Graphic libraries and applications (graphic/text) ---> [*] X.org X Window System ---> X11R7 Servers ---> [*] xorg-server X Window System server type (KDrive / TinyX) ---> [ ] Null root cursor [ ] Enable AIGLX Extension [*] Enable KDrive/TinyX evdev input driver [*] Enable KDrive/TinyX kbd input driver [*] Enable KDrive/TinyX mouse input driver *** Optional Servers *** [ ] Xvfb server ... X11R7 Applications ---> ... [*] xclock ... [*] xeyes ... [*] xterm
Launching
- For example, with a mouse and a keyboard (event0):
# /usr/bin/X -mouse evdev -retro -keybd evdev,,device=/dev/input/event0 &
- Or with a touchscreen (event0):
# /usr/bin/X -retro -mouse tslib,,device=/dev/input/event0 &
then you will need to launch a window manager (like Matchbox or Blackbox) and some applications....
# xterm & # xeyes &