I want to participate in EVoC with Wayland and Linux, how to start?
ppaalanen at gmail.com
Mon Jul 2 09:54:36 UTC 2018
On Sun, 1 Jul 2018 20:03:36 +0300
Denis Obrezkov <denisobrezkov at gmail.com> wrote:
> I am a phd student and I would like to participate in Endless Vacation
> of Code:
> I have read wayland documentation and started to read the Linux GPU
> Driver Developers' guide. I also found some interesting project:
That's the atomic modesetting feature. The basics have landed, Daniel
has a remaining series brewing for restoring the composite bypass path
and using hardware planes. What hasn't been worked on yet AFAIK is the
TEST_ONLY feature of atomic modesetting. Essentially, before we take an
output configuration into use, we should do a TEST_ONLY commit to see
if it possible before-hand, rather than failing after the configuration
is used. TEST_ONLY would allow iterating through different
configurations to see which ones should work.
> and I found a label called "Good for new contributors". But right now I
> don't understand where and how to start. For example, how a typical
> working environment looks like? Should I use wayland in some distro or
> should I build on top of a bare kernel with glibc?
You run a distribution you like and are familiar with. You can use
distribution packages for all components you don't need to modify and
are new enough. Set up a prefix under your home directory where you
install all the software you need to build manually. Getting Weston
built manually and running from a prefix directory would be the first
Atomic modesetting is exclusive to the DRM-backend, so you should be
prepared to run Weston from the virtual terminal on "bare" hardware. If
something goes wrong, it is very handy to have another computer to log
in remotely to diagnose and recover. Virtual machines like qemu are not
always suitable for testing the DRM-backend.
Also note that NVIDIA proprietary drivers are not suitable for working
> Also, I have some organizational questions about evoc, e.g. about its
> duration, about possible mentor, etc.
These I cannot personally help with, sorry.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 833 bytes
Desc: OpenPGP digital signature
More information about the wayland-devel