You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
Kristian Høgsberg f9112b2de0 Fix X button and keycodes 15 years ago
clients Split native drm part of compositor out 15 years ago
spec Split native drm part of compositor out 15 years ago
.gitignore Split native drm part of compositor out 15 years ago
70-wayland.rules Update udev rules to work with new udev 15 years ago
Makefile Add x11 backend for compositor 15 years ago
NOTES Drop stuff from notes that are in the spec now 15 years ago
README README: Add link to google group. 16 years ago
TODO Update todo 15 years ago
cairo-util.c Tweak theme a bit 15 years ago
cairo-util.h Put Wayland under the MIT license. 16 years ago
compositor-drm.c Add x11 backend for compositor 15 years ago
compositor-x11.c Fix X button and keycodes 15 years ago
compositor.c Fix X button and keycodes 15 years ago
compositor.h Add x11 backend for compositor 15 years ago
config.mk.in Send device name at connect time 15 years ago
configure.ac Add x11 backend for compositor 15 years ago
connection.c Import Eric Anholts hash table implementation 15 years ago
connection.h Import Eric Anholts hash table implementation 15 years ago
event-loop.c Add x11 backend for compositor 15 years ago
screenshooter.c Split native drm part of compositor out 15 years ago
wayland-client.c Drop surface::copy 15 years ago
wayland-client.h Add extern "C" wrappers to public header files 15 years ago
wayland-hash.c Import Eric Anholts hash table implementation 15 years ago
wayland-protocol.c Send device name at connect time 15 years ago
wayland-protocol.h Add extern "C" wrappers to public header files 15 years ago
wayland-server.pc.in Install libraries plus headers and add pkg-config files. 16 years ago
wayland-util.c Import Eric Anholts hash table implementation 15 years ago
wayland-util.h Add extern "C" wrappers to public header files 15 years ago
wayland.c Send device name at connect time 15 years ago
wayland.h Add extern "C" wrappers to public header files 15 years ago
wayland.pc.in Install libraries plus headers and add pkg-config files. 16 years ago

README

This file describes how to build and run wayland.  See NOTES for what
wayland is or maybe will be some day. There's a google group for
wayland/eagle discussion here:

http://groups.google.com/group/wayland-display-server

Wayland requires the eagle EGL stack available from

git://people.freedesktop.org/~krh/eagle

and currently assumes that eagle is checked out in a sibling
directory, for example:

~krh/src/wayland and
~krh/src/eagle

Eagle should work with a recent DRI driver from mesa, but I have mesa
repo with an eagle branch here:

git://people.freedesktop.org/~krh/mesa

which provides and experimental DRI CopyBuffer extension, that lets
wayland use the DRI driver and the hardware for implementing buffer
swaps. Eagle needs to be compiled against the dri_interface.h from
this branch to be able to use the CopyBuffer extension.

To run wayland you currently need intel hardware, a kernel with gem
and kernel modesetting, and it is necessary to set a couple of
environment variables. First, set LD_LIBRARY_PATH:

export LD_LIBRARY_PATH=$PWD:$PWD/../eagle

Yes, this sucks, but libtool sucks more. Then to let eagle pick up
the custom dri driver, set

export EAGLE_DRIVER_PATH=$PWD/../mesa/lib

and finally set up the path to the evdev device to use as a pointer
device:

export WAYLAND_POINTER=/dev/by-id/whatever-it's-called-event-mouse

If you haven't already, load the i915 driver with modesetting:

modprobe i915 modeset=1

You may need to unload it first, if it's loaded already. Also, on
Fedora, there may be a bogus /etc/modprobe.d/i915modeset preventing
the modeset paramater from reaching the module. Nuke it.

At this point you should be able to launch wayland and a couple of
clients. Try something like:

./wayland &
./background <some png/jpg image smaller than 1024x768> &
./flower &
./flower &
./flower &
./window &
./pointer &

Maybe some day there'll be a script that does all this. Some day...

And after all this work it may still not work or even oops your
kernel. It's very much work in progress, so be prepared.

cheers,
Kristian