Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
W
weston
Manage
Activity
Members
Labels
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Model registry
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Pekka Paalanen
weston
Commits
33a52bd0
Commit
33a52bd0
authored
16 years ago
by
Kristian Høgsberg
Browse files
Options
Downloads
Patches
Plain Diff
Add README for the adventurous, allow evdev override from getenv().
parent
35370f80
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
README
+65
-0
65 additions, 0 deletions
README
wayland.c
+7
-1
7 additions, 1 deletion
wayland.c
with
72 additions
and
1 deletion
README
0 → 100644
+
65
−
0
View file @
33a52bd0
This file describes how to build and run wayland. See NOTES for what
wayland is or maybe will be some day.
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
This diff is collapsed.
Click to expand it.
wayland.c
+
7
−
1
View file @
33a52bd0
...
...
@@ -484,7 +484,13 @@ static const char input_device_file[] =
static
void
wl_display_create_input_devices
(
struct
wl_display
*
display
)
{
display
->
pointer
=
wl_input_device_create
(
display
,
input_device_file
,
1
);
const
char
*
path
;
path
=
getenv
(
"WAYLAND_POINTER"
);
if
(
path
==
NULL
)
path
=
input_device_file
;
display
->
pointer
=
wl_input_device_create
(
display
,
path
,
1
);
if
(
display
->
pointer
!=
NULL
)
wl_hash_insert
(
&
display
->
objects
,
display
->
pointer
);
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment