On my CoffeeLake machine, when build i915 driver as kernel module,
will got following error message in Xorg.0.log:
(EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
When compile i915 as kernel module, drm device won't be initiated
after rootfs was mounted. This may
On Wed, Apr 11, 2018 at 03:39:33PM -0400, Adam Jackson wrote:
> Apparently on NetBSD we can hit failures like this:
>
> sdksyms.c:1773:15: error: expected expression before ',' token
> (void *) &, /*
> ../../dri3/dri3.h:110 */
>
> I've been
On my CoffeeLake S board, after compile i915 as a kernel module
will got following error in Xorg.0.log:
(EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission
denied
(EE) open /dev/fb0: No such file or directory
This is a timing proble between i915 driver and Xorg,
add
After compile i915 driver as kernel module, will got error message:
(EE) open /dev/fb0: No such file or directory
This is because i915 driver did not finish fb initialized work
while process trying to open it. This is still a timing problem between
i915.ko and Xorg
Add a loop to wait i915 driver
I'm wondering if it's this commit that added it back in January
commit 7617a0a180a2cd3427a8ffa9534152df6a8fecbf
Author: Qiang Yu
Date: Wed Jan 11 13:59:22 2017 +0800
dri2: refine dri2_probe_driver_name (v2)
V2:
1. update comment
2. check bustype if PCI
3.
I've also noticed the AMDGPU powers up each time I play a video -
either using SMplayer or on Chromium
[50458.810260] snd_hda_codec_ca0132 hdaudioC0D0: ca0132 DSP downloaded
and running
[50459.699224] [drm] PCIE GART of 1024M enabled (table at 0x00F4).
[50459.797265] [drm] UVD
The journal.freeze I mentioned but was too big to attach
On 11 April 2018 at 22:53, Mike Lothian wrote:
> Hi
>
> Hopefully 3rd time lucky (sorry Roman)
>
> I've done some more testing. The flashing I was seeing with Xserver
> 1.19.5 goes away when I use egl rather then glx
Hi
Hopefully 3rd time lucky (sorry Roman)
I've done some more testing. The flashing I was seeing with Xserver
1.19.5 goes away when I use egl rather then glx with Kwin - I won't be
using egl in any of the next tests
When I use Xserver 1.20 RC4 with Intel/AMDPGU DDXs Kwin doesn't start
- the X
On Wed, Apr 11, 2018 at 2:44 AM, Thomas Klausner wrote:
> I still see this build failure on NetBSD:
>
> sdksyms.c:1773:15: error: expected expression before ',' token
> (void *) &, /*
> ../../dri3/dri3.h:110 */
>
On 04/10/18 01:52 PM, alexander@wellsfargo.com wrote:
> I have been scouring every knowledgebase available to me including exceed/open
> text resource to figure out why my application is crashing. I basically use
> exceed to export the display to my windows pc. So far this week, I had 5
>
I have been scouring every knowledgebase available to me including exceed/open
text resource to figure out why my application is crashing. I basically use
exceed to export the display to my windows pc. So far this week, I had 5
crashes. Wondering if anyone knows or have dealt with this in
Apparently on NetBSD we can hit failures like this:
sdksyms.c:1773:15: error: expected expression before ',' token
(void *) &, /*
../../dri3/dri3.h:110 */
I've been unable to reproduce that locally (even in a NetBSD vm), but
an obvious
From: Emil Velikov
Replace the current (incorrect) assumption that wayland-scanner is
located in the wayland-client prefix. Make use of the wayland_scanner
variable in wayland-scanner.pc
It was introduced back in 2013 and we already require newer wayland bits
Ilya,
1.
/usr/share/X11/locale/locale.dir
does contain the line
en_US.UTF-8/XLC_LOCALE: en_HK.UTF-8
2.
/usr/share/X11/locale/locale.alias
doesn't contain a line beginning with
en_HK.UTF-8:
does contain lines beginning with
en_HK.utf8, en_HK.iso88591, etc.
3.
/etc/locale.gen
is
On Wed, 2018-04-11 at 09:44 +0200, Thomas Klausner wrote:
> I still see this build failure on NetBSD:
>
> sdksyms.c:1773:15: error: expected expression before ',' token
> (void *) &, /*
> ../../dri3/dri3.h:110 */
>^
I'm
Hey Adam,
On Wed, Apr 11, 2018 at 4:40 PM, Adam Jackson wrote:
> On Wed, 2018-04-11 at 09:49 +0200, Olivier Fourdan wrote:
>
> > What are the risks of landing it? It would break for hardware/driver
> > which are not supported yet anyway?
>
> The code it adds basically only runs
On Wed, 2018-04-11 at 09:49 +0200, Olivier Fourdan wrote:
> What are the risks of landing it? It would break for hardware/driver
> which are not supported yet anyway?
The code it adds basically only runs on NVIDIA's drivers, since nobody
else supports EGL_KHR_streams (as far as I'm aware, at
Adam Jackson wrote:
> the deafening silence of review feedback has not been encouraging.
I've just subscribed to this list only to give my feedback about
EGLStreams into XWayland, but I can't give any real review, only opinions.
I don't know what the policies are, but I feel like including
Hi Adam,
[Re-sending to xorg-devel where this was intended, sorry!]
On 10 April 2018 at 21:57, Adam Jackson wrote:
> Another batch of cleanups and fixes, mostly in glamor and DRI3.
>
> At this point the only outstanding major feature for 1.20 that hasn't
> landed yet is
Hi all.I would like to be able to raise the clicked window to the top of the
stack on my window manager. But it fail because only one client can SelectInput
on Button events at one time. How can I realize my goal? Here is my code :
#include
int main(void)
{
Display
I still see this build failure on NetBSD:
sdksyms.c:1773:15: error: expected expression before ',' token
(void *) &, /*
../../dri3/dri3.h:110 */
^
Thomas
On Tue, Apr 10, 2018 at 03:57:25PM -0400, Adam Jackson wrote:
>
Hi Adam,
On 10 April 2018 at 21:57, Adam Jackson wrote:
> Another batch of cleanups and fixes, mostly in glamor and DRI3.
>
> At this point the only outstanding major feature for 1.20 that hasn't
> landed yet is EGLStreams support for Xwayland. The patches require some
> minor
22 matches
Mail list logo