January 30, 2016 at 8:35 pm #67384dimkoParticipant
Need some sleep and will try to figure out how to make it work on it’s own.(providing driver allows)
Initial thoughts, didn’t notice major performance difference.
I did, however, noticed, that tearing issue was no more(or so comrade thinks in his wishful tsinking?)
Would be awesome to see it working on it’s own, but your sincere comrade needs sleeping.
He also needs girlfriend. Pedro, may be, he is very pretty boy, zis Pedro.
I offered Venn to be my girlfriend, but he refused.
I don’t like Jews, though…January 30, 2016 at 8:50 pm #75735dimkoParticipant
screenshot was made on AMD64 Gentoo
When running westom from console, comrade gets this:
Date: 2016-01-31 GMT
[02:06:28.089] weston 1.9.0
Bug reports to: https://bugs.freedesktop.org/enter_bug. … sion=1.9.0
Build: 1.8.93-2-gb05cdb8 configure.ac: bump to version 1.9.0 for the official release (2015-09-21 18:11:26 -0700)
[02:06:28.089] OS: Linux, 4.4.0, #2 SMP Sun Jan 31 01:31:24 GMT 2016, x86_64
[02:06:28.089] Starting with no config file.
[02:06:28.089] Loading module ‘/usr/lib64/weston/drm-backend.so’
[02:06:28.093] Output repaint window is 7 ms maximum.
[02:06:28.093] initializing drm backend
[02:06:28.099] logind: using VT /dev/tty4
[02:06:28.099] logind: session control granted
[02:06:28.099] no drm device found
[02:06:28.099] fatal: failed to create compositor backend
This no drm device message upsets comrade much, but makes comrade trust nvidia to do right thing.
It feels, like nvidia WILL deliver Vulkan + Weston/Wayland support this year.
- You must be logged in to reply to this topic.