Linaro Tech Days: Wayland, Weston & Open Source GPU drivers
Hi, This week, Daniel Stone and Tomeu Vizoso will be taking part in Linaro Tech Days, a series of technical sessions presented live online via Zoom webinar and streamed on YouTube. These sessions are *free* to attend & open to all. On Wednesday, Daniel presents "Wayland and Weston: 8 years of production devices", a in-depth look at how far Wayland has come (bound to be super interesting), while on Thursday, Tomeu Vizoso will be presenting & hosting a Open Source GPU drivers BoF, with a look at what's to come in 2020 with multiple teams from the community joining the conversation. Below are the details of the two presentations: 1) "Wayland and Weston: 8 years of production devices" Presented by Daniel Stone – Wednesday, April 1, 16:00 GMT. 2) "Open Source GPU Drivers BoF" Presented by Tomeu Vizoso – Thursday, April 2, 15:00 GMT. Links here: https://www.collabora.com/news-and-blog/news-and-events/linaro-tech-days-wayland-weston-open-source-gpu-drivers.html Mark ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
Re: RFC: Minimum meson version for xserver 20
On 2020-03-30 5:23 p.m., Adam Jackson wrote: > Does anyone have strong opinions on this? I would really like to bump > to at least 0.49 for the position-independent executable support. If > not that, 0.47 gives us 'feature' support for build options, which > addresses the "should we enable this by default or not" question in a > consistent way. Even stock Debian stable has 0.49.2 (backports has 0.52.1), so 0.49 seems fair game. -- Earthling Michel Dänzer | https://redhat.com Libre software enthusiast | Mesa and X developer ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
RFC: Minimum meson version for xserver 20
Does anyone have strong opinions on this? I would really like to bump to at least 0.49 for the position-independent executable support. If not that, 0.47 gives us 'feature' support for build options, which addresses the "should we enable this by default or not" question in a consistent way. - ajax ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
[PATCH xserver] Xorg.wrap: Fix the console check on DragonFly
DragonFly can use the same VT_GETINDEX ioctl mechanism as the existing FreeBSD code. Signed-off-by: François Tigeot --- hw/xfree86/xorg-wrapper.c | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/hw/xfree86/xorg-wrapper.c b/hw/xfree86/xorg-wrapper.c index 6c1022358..680646951 100644 --- a/hw/xfree86/xorg-wrapper.c +++ b/hw/xfree86/xorg-wrapper.c @@ -39,7 +39,8 @@ #include #endif #include -#if defined(__FreeBSD__) || defined(__FreeBSD_kernel__) +#if defined(__FreeBSD__) || defined(__FreeBSD_kernel__) || \ +defined(__DragonFly__) #include #endif #include @@ -170,7 +171,8 @@ static int on_console(int fd) r = fstat(fd, ); if (r == 0 && S_ISCHR(st.st_mode) && major(st.st_rdev) == 4) return 1; -#elif defined(__FreeBSD__) || defined(__FreeBSD_kernel__) +#elif defined(__FreeBSD__) || defined(__FreeBSD_kernel__) || \ + defined(__DragonFly__) int idx; if (ioctl(fd, VT_GETINDEX, ) != -1) -- 2.25.1 ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
