82f91433e2
Glamor has a mode where pixmaps will be constructed from numerous small FBOs. This allows testing of the tiled pixmap code without needing to create huge pixmaps. However, the render glyph code assumed that it could create a pixmap large enough for the glyph atlas. Instead of attempting to fix that (which would be disruptive and not helpful), I've added a new pixmap creation usage, GLAMOR_CREATE_NO_LARGE which forces allocation of a single large FBO. Now that we have pixmaps with varying FBO sizes, I then went around and fixed the few places using the global FBO max size and replaced that with the per-pixmap FBO tiling sizes, which were already present in each large pixmap. Xephyr has been changed to pass GLAMOR_CREATE_NO_LARGE when it creates the screen pixmap as it doesn't want to deal with tiling either. Signed-off-by: Keith Packard <keithp@keithp.com> Signed-off-by: Eric Anholt <eric@anholt.net> Reviewed-by: Eric Anholt <eric@anholt.net> |
||
---|---|---|
.. | ||
man | ||
.gitignore | ||
ephyr_draw.c | ||
ephyr_glamor_glx.c | ||
ephyr_glamor_glx.h | ||
ephyr.c | ||
ephyr.h | ||
ephyrdri.c | ||
ephyrdri.h | ||
ephyrdriext.c | ||
ephyrdriext.h | ||
ephyrglxext.c | ||
ephyrglxext.h | ||
ephyrhostglx.c | ||
ephyrhostglx.h | ||
ephyrinit.c | ||
ephyrlog.h | ||
ephyrvideo.c | ||
hostx.c | ||
hostx.h | ||
Makefile.am | ||
os.c | ||
README |
Xephyr README ============= What Is It ? ============ Xephyr is a a kdrive server that outputs to a window on a pre-existing 'host' X display. Think Xnest but with support for modern extensions like composite, damage and randr. Unlike Xnest which is an X proxy, i.e. limited to the capabilities of the host X server, Xephyr is a real X server which uses the host X server window as "framebuffer" via fast SHM XImages. It also has support for 'visually' debugging what the server is painting. How To Use ========== You probably want to run like; Xephyr :1 -ac -screen 800x600 & Then set DISPLAY=:1 and run whatever X apps you like. Use 'xrandr' to change to orientation/size. There is a '-parent' switch which works just like Xnests ( for use with things like matchbox-nest - http://matchbox.handhelds.org ). There is also a '-host-cursor' switch to set 'cursor acceleration' - The host's cursor is reused. This is only really there to aid debugging by avoiding server paints for the cursor. Performance improvement is negiable. Send a SIGUSR1 to the server ( eg kill -USR1 `pidof Xephyr` ) to toggle the debugging mode. In this mode red rectangles are painted to screen areas getting painted before painting the actual content. The delay between this can be altered by setting a XEPHYR_PAUSE env var to a value in micro seconds. Caveats ======= - Depth is limited to being the same as the host. *Update* As of 8/11/2004. Xephyr can now do 8bpp & 16bpp on 24bpp host. - Rotated displays are currently updated via full blits. This is slower than a normal oprientated display. Debug mode will therefor not be of much use rotated. - The '-host-cursor' cursor is static in its appearence. - The build gets a warning about 'nanosleep'. I think the various '-D' build flags are causing this. I havn't figured as yet how to work round it. It doesn't appear to break anything however. - Keyboard handling is basic but works. - Mouse button 5 probably wont work. Matthew Allum <mallum@o-hand.com> 2004