Skip to contentSkip to conversation

drm/vmwgfx: Work around drm removal of control nodes

PATCH Applied Thomas Hellstrom 3 participants 7 messages Feb 21, 2017 – Feb 26, 2017

Subsystems (4)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 drm/vmwgfx: Work around drm removal of control nodes

vmware tools has a daemon that gets layout information from the GUI and forwards it to DRM so that the modesetting code can set preferred connector locations and modes. This daemon was using control nodes but since control nodes were just removed, make it possible for the daemon to use render- or primary nodes instead. This is a bit ugly but will allow drm to proceed with removal of the mostly unused control-node code and allow vmware to proceed with fixing up automatic layout settings for gnome-shell/wayland.

We bump minor to inform user-space about the api change.

---
 drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 11 ++++++++++-
 drivers/gpu/drm/vmwgfx/vmwgfx_drv.h |  4 ++--
 2 files changed, 12 insertions(+), 3 deletions(-)
drivers/gpu/drm/vmwgfx/vmwgfx_drv.c +10 -1
index 541a588..d08f269 100644
@@ -199,9 +199,14 @@ static const struct drm_ioctl_desc vmw_ioctls[] = {
 	VMW_IOCTL_DEF(VMW_PRESENT_READBACK,
 		      vmw_present_readback_ioctl,
 		      DRM_MASTER | DRM_AUTH),
+	/*
+	 * The permissions of the below ioctl are overridden in
+	 * vmw_generic_ioctl(). We require either
+	 * DRM_MASTER or capable(CAP_SYS_ADMIN).
+	 */
 	VMW_IOCTL_DEF(VMW_UPDATE_LAYOUT,
 		      vmw_kms_update_layout_ioctl,
-		      DRM_MASTER | DRM_CONTROL_ALLOW),
+		      DRM_RENDER_ALLOW),
 	VMW_IOCTL_DEF(VMW_CREATE_SHADER,
 		      vmw_shader_define_ioctl,
 		      DRM_AUTH | DRM_RENDER_ALLOW),
@@ -1123,6 +1128,10 @@ static long vmw_generic_ioctl(struct file *filp, unsigned int cmd,
 
 			return (long) vmw_execbuf_ioctl(dev, arg, file_priv,
 							_IOC_SIZE(cmd));
+		} else if (nr == DRM_COMMAND_BASE + DRM_VMW_UPDATE_LAYOUT) {
+			if (!drm_is_current_master(file_priv) &&
+			    !capable(CAP_SYS_ADMIN))
+				return -EACCES;
 		}
 
 		if (unlikely(ioctl->cmd != cmd))
drivers/gpu/drm/vmwgfx/vmwgfx_drv.h +2 -2
index 1e59a48..59ff419 100644
@@ -41,9 +41,9 @@
 #include <drm/ttm/ttm_module.h>
 #include "vmwgfx_fence.h"
 
-#define VMWGFX_DRIVER_DATE "20160210"
+#define VMWGFX_DRIVER_DATE "20170221"
 #define VMWGFX_DRIVER_MAJOR 2
-#define VMWGFX_DRIVER_MINOR 11
+#define VMWGFX_DRIVER_MINOR 12
 #define VMWGFX_DRIVER_PATCHLEVEL 0
 #define VMWGFX_FILE_PAGE_OFFSET 0x00100000
 #define VMWGFX_FIFO_STATIC_SIZE (1024*1024)
Signature · 1 line
2.9.3
Reviewed-by on v1 1/1
#1 lore raw
Quoted 67 lines · Thomas Hellstrom

vmware tools has a daemon that gets layout information from the GUI and forwards it to DRM so that the modesetting code can set preferred connector locations and modes. This daemon was using control nodes but since control nodes were just removed, make it possible for the daemon to use render- or primary nodes instead. This is a bit ugly but will allow drm to proceed with removal of the mostly unused control-node code and allow vmware to proceed with fixing up automatic layout settings for gnome-shell/wayland.

We bump minor to inform user-space about the api change.

---
 drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 11 ++++++++++-
 drivers/gpu/drm/vmwgfx/vmwgfx_drv.h |  4 ++--
 2 files changed, 12 insertions(+), 3 deletions(-)
drivers/gpu/drm/vmwgfx/vmwgfx_drv.c +10 -1
index 541a588..d08f269 100644
@@ -199,9 +199,14 @@ static const struct drm_ioctl_desc vmw_ioctls[] = {
 	VMW_IOCTL_DEF(VMW_PRESENT_READBACK,
 		      vmw_present_readback_ioctl,
 		      DRM_MASTER | DRM_AUTH),
+	/*
+	 * The permissions of the below ioctl are overridden in
+	 * vmw_generic_ioctl(). We require either
+	 * DRM_MASTER or capable(CAP_SYS_ADMIN).
+	 */
 	VMW_IOCTL_DEF(VMW_UPDATE_LAYOUT,
 		      vmw_kms_update_layout_ioctl,
-		      DRM_MASTER | DRM_CONTROL_ALLOW),
+		      DRM_RENDER_ALLOW),
 	VMW_IOCTL_DEF(VMW_CREATE_SHADER,
 		      vmw_shader_define_ioctl,
 		      DRM_AUTH | DRM_RENDER_ALLOW),
@@ -1123,6 +1128,10 @@ static long vmw_generic_ioctl(struct file *filp, unsigned int cmd,
 
 			return (long) vmw_execbuf_ioctl(dev, arg, file_priv,
 							_IOC_SIZE(cmd));
+		} else if (nr == DRM_COMMAND_BASE + DRM_VMW_UPDATE_LAYOUT) {
+			if (!drm_is_current_master(file_priv) &&
+			    !capable(CAP_SYS_ADMIN))
+				return -EACCES;
 		}
 
 		if (unlikely(ioctl->cmd != cmd))
drivers/gpu/drm/vmwgfx/vmwgfx_drv.h +2 -2
index 1e59a48..59ff419 100644
@@ -41,9 +41,9 @@
 #include <drm/ttm/ttm_module.h>
 #include "vmwgfx_fence.h"
 
-#define VMWGFX_DRIVER_DATE "20160210"
+#define VMWGFX_DRIVER_DATE "20170221"
 #define VMWGFX_DRIVER_MAJOR 2
-#define VMWGFX_DRIVER_MINOR 11
+#define VMWGFX_DRIVER_MINOR 12
 #define VMWGFX_DRIVER_PATCHLEVEL 0
 #define VMWGFX_FILE_PAGE_OFFSET 0x00100000
 #define VMWGFX_FIFO_STATIC_SIZE (1024*1024)
Signature · 1 line
2.9.3
#2 lore raw
Quoted 1 line · Sinclair Yeh

Applied to drm-msic-next-fixes, I'll send the pull request asap. -Daniel

Quoted 74 lines · Thomas Hellstrom
Quoted 67 lines

vmware tools has a daemon that gets layout information from the GUI and forwards it to DRM so that the modesetting code can set preferred connector locations and modes. This daemon was using control nodes but since control nodes were just removed, make it possible for the daemon to use render- or primary nodes instead. This is a bit ugly but will allow drm to proceed with removal of the mostly unused control-node code and allow vmware to proceed with fixing up automatic layout settings for gnome-shell/wayland.

We bump minor to inform user-space about the api change.

---
 drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 11 ++++++++++-
 drivers/gpu/drm/vmwgfx/vmwgfx_drv.h |  4 ++--
 2 files changed, 12 insertions(+), 3 deletions(-)
drivers/gpu/drm/vmwgfx/vmwgfx_drv.c +10 -1
index 541a588..d08f269 100644
@@ -199,9 +199,14 @@ static const struct drm_ioctl_desc vmw_ioctls[] = {
 	VMW_IOCTL_DEF(VMW_PRESENT_READBACK,
 		      vmw_present_readback_ioctl,
 		      DRM_MASTER | DRM_AUTH),
+	/*
+	 * The permissions of the below ioctl are overridden in
+	 * vmw_generic_ioctl(). We require either
+	 * DRM_MASTER or capable(CAP_SYS_ADMIN).
+	 */
 	VMW_IOCTL_DEF(VMW_UPDATE_LAYOUT,
 		      vmw_kms_update_layout_ioctl,
-		      DRM_MASTER | DRM_CONTROL_ALLOW),
+		      DRM_RENDER_ALLOW),
 	VMW_IOCTL_DEF(VMW_CREATE_SHADER,
 		      vmw_shader_define_ioctl,
 		      DRM_AUTH | DRM_RENDER_ALLOW),
@@ -1123,6 +1128,10 @@ static long vmw_generic_ioctl(struct file *filp, unsigned int cmd,
 
 			return (long) vmw_execbuf_ioctl(dev, arg, file_priv,
 							_IOC_SIZE(cmd));
+		} else if (nr == DRM_COMMAND_BASE + DRM_VMW_UPDATE_LAYOUT) {
+			if (!drm_is_current_master(file_priv) &&
+			    !capable(CAP_SYS_ADMIN))
+				return -EACCES;
 		}
 
 		if (unlikely(ioctl->cmd != cmd))
drivers/gpu/drm/vmwgfx/vmwgfx_drv.h +2 -2
index 1e59a48..59ff419 100644
@@ -41,9 +41,9 @@
 #include <drm/ttm/ttm_module.h>
 #include "vmwgfx_fence.h"
 
-#define VMWGFX_DRIVER_DATE "20160210"
+#define VMWGFX_DRIVER_DATE "20170221"
 #define VMWGFX_DRIVER_MAJOR 2
-#define VMWGFX_DRIVER_MINOR 11
+#define VMWGFX_DRIVER_MINOR 12
 #define VMWGFX_DRIVER_PATCHLEVEL 0
 #define VMWGFX_FILE_PAGE_OFFSET 0x00100000
 #define VMWGFX_FIFO_STATIC_SIZE (1024*1024)
Signature · 1 line
2.9.3

_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Signature · 3 lines
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
#3 lore raw
In reply to Thomas Hellstrom
Quoted 8 lines · Thomas Hellstrom

vmware tools has a daemon that gets layout information from the GUI and forwards it to DRM so that the modesetting code can set preferred connector locations and modes. This daemon was using control nodes but since control nodes were just removed, make it possible for the daemon to use render- or primary nodes instead. This is a bit ugly but will allow drm to proceed with removal of the mostly unused control-node code and allow vmware to proceed with fixing up automatic layout settings for gnome-shell/wayland.

Quoted 4 lines

We bump minor to inform user-space about the api change.

Seems reasonable. I guess with hindsight we probably should have added a virtual_x/y hint, similar to the hotpsot hinting we do for cursors. But since vmwgfx is the only virtual gpu that seems to do multi-screen that need was never all that apparent. I think we should fix that if/when vmwgfx switches over to atomic, atomic is super easy to extend. Also, with this patch I think we can restore backwards compat by registering the render node as controlD (but only for vmwgfx, we'll keep the fake symlink for everyone else). I'm travelling still till the end of this week, and my brain is wrecked, but will get to that as soon as I'm back next week. I'll also reference the link in that commit.

Cheers, Daniel

Quoted 59 lines
---
 drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 11 ++++++++++-
 drivers/gpu/drm/vmwgfx/vmwgfx_drv.h |  4 ++--
 2 files changed, 12 insertions(+), 3 deletions(-)
drivers/gpu/drm/vmwgfx/vmwgfx_drv.c +10 -1
index 541a588..d08f269 100644
@@ -199,9 +199,14 @@ static const struct drm_ioctl_desc vmw_ioctls[] = {
        VMW_IOCTL_DEF(VMW_PRESENT_READBACK,
                      vmw_present_readback_ioctl,
                      DRM_MASTER | DRM_AUTH),
+       /*
+        * The permissions of the below ioctl are overridden in
+        * vmw_generic_ioctl(). We require either
+        * DRM_MASTER or capable(CAP_SYS_ADMIN).
+        */
        VMW_IOCTL_DEF(VMW_UPDATE_LAYOUT,
                      vmw_kms_update_layout_ioctl,
-                     DRM_MASTER | DRM_CONTROL_ALLOW),
+                     DRM_RENDER_ALLOW),
        VMW_IOCTL_DEF(VMW_CREATE_SHADER,
                      vmw_shader_define_ioctl,
                      DRM_AUTH | DRM_RENDER_ALLOW),
@@ -1123,6 +1128,10 @@ static long vmw_generic_ioctl(struct file *filp, unsigned int cmd,
 
                        return (long) vmw_execbuf_ioctl(dev, arg, file_priv,
                                                        _IOC_SIZE(cmd));
+               } else if (nr == DRM_COMMAND_BASE + DRM_VMW_UPDATE_LAYOUT) {
+                       if (!drm_is_current_master(file_priv) &&
+                           !capable(CAP_SYS_ADMIN))
+                               return -EACCES;
                }
 
                if (unlikely(ioctl->cmd != cmd))
drivers/gpu/drm/vmwgfx/vmwgfx_drv.h +2 -3
index 1e59a48..59ff419 100644
@@ -41,9 +41,9 @@
 #include <drm/ttm/ttm_module.h>
 #include "vmwgfx_fence.h"
 
-#define VMWGFX_DRIVER_DATE "20160210"
+#define VMWGFX_DRIVER_DATE "20170221"
 #define VMWGFX_DRIVER_MAJOR 2
-#define VMWGFX_DRIVER_MINOR 11
+#define VMWGFX_DRIVER_MINOR 12
 #define VMWGFX_DRIVER_PATCHLEVEL 0
 #define VMWGFX_FILE_PAGE_OFFSET 0x00100000
 #define VMWGFX_FIFO_STATIC_SIZE (1024*1024)
--

2.9.3

_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Signature · 7 lines
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
#4 lore raw
Quoted 10 lines · Daniel Vetter
Quoted 8 lines · Thomas Hellstrom

vmware tools has a daemon that gets layout information from the GUI and forwards it to DRM so that the modesetting code can set preferred connector locations and modes. This daemon was using control nodes but since control nodes were just removed, make it possible for the daemon to use render- or primary nodes instead. This is a bit ugly but will allow drm to proceed with removal of the mostly unused control-node code and allow vmware to proceed with fixing up automatic layout settings for gnome-shell/wayland.

Quoted 5 lines
Quoted 4 lines

We bump minor to inform user-space about the api change.

Seems reasonable.

So is this an Acked-by?

Quoted 6 lines

I guess with hindsight we probably should have added
a virtual_x/y hint, similar to the hotpsot hinting we do for cursors. But since vmwgfx is the only virtual gpu that seems to do multi-screen that need was never all that apparent. I think we should fix that if/when vmwgfx switches over to atomic, atomic is super easy to extend.

Yes. I think we're open to a way to make this fit into the atomic infrastructure. We should remember though that other virtual GPUs may get this information from the virtual device rather than from user-space. The reason the information still originates from user-space in the VMware environment is the need to support remote screen layouts from a guest.

Quoted 3 lines

Also, with this patch I think we can restore backwards compat
by registering the render node as controlD (but only for vmwgfx, we'll keep the fake symlink for everyone else).

Actually, given that the feature was pulled out of the openSuSE and Fedora packages at the very last minute, it seems like we can skip the special VMware control node setup. The damage will be limited to within VMware.

Quoted 6 lines

I'm travelling still till
the end of this week, and my brain is wrecked, but will get to that as soon as I'm back next week. I'll also reference the link in that commit.

Cheers, Daniel

Thanks,
Thomas

Quoted 56 lines
Quoted 56 lines
---
 drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 11 ++++++++++-
 drivers/gpu/drm/vmwgfx/vmwgfx_drv.h |  4 ++--
 2 files changed, 12 insertions(+), 3 deletions(-)
drivers/gpu/drm/vmwgfx/vmwgfx_drv.c +10 -1
index 541a588..d08f269 100644
@@ -199,9 +199,14 @@ static const struct drm_ioctl_desc vmw_ioctls[] = {
        VMW_IOCTL_DEF(VMW_PRESENT_READBACK,
                      vmw_present_readback_ioctl,
                      DRM_MASTER | DRM_AUTH),
+       /*
+        * The permissions of the below ioctl are overridden in
+        * vmw_generic_ioctl(). We require either
+        * DRM_MASTER or capable(CAP_SYS_ADMIN).
+        */
        VMW_IOCTL_DEF(VMW_UPDATE_LAYOUT,
                      vmw_kms_update_layout_ioctl,
-                     DRM_MASTER | DRM_CONTROL_ALLOW),
+                     DRM_RENDER_ALLOW),
        VMW_IOCTL_DEF(VMW_CREATE_SHADER,
                      vmw_shader_define_ioctl,
                      DRM_AUTH | DRM_RENDER_ALLOW),
@@ -1123,6 +1128,10 @@ static long vmw_generic_ioctl(struct file *filp, unsigned int cmd,
 
                        return (long) vmw_execbuf_ioctl(dev, arg, file_priv,
                                                        _IOC_SIZE(cmd));
+               } else if (nr == DRM_COMMAND_BASE + DRM_VMW_UPDATE_LAYOUT) {
+                       if (!drm_is_current_master(file_priv) &&
+                           !capable(CAP_SYS_ADMIN))
+                               return -EACCES;
                }
 
                if (unlikely(ioctl->cmd != cmd))
drivers/gpu/drm/vmwgfx/vmwgfx_drv.h +2 -3
index 1e59a48..59ff419 100644
@@ -41,9 +41,9 @@
 #include <drm/ttm/ttm_module.h>
 #include "vmwgfx_fence.h"
 
-#define VMWGFX_DRIVER_DATE "20160210"
+#define VMWGFX_DRIVER_DATE "20170221"
 #define VMWGFX_DRIVER_MAJOR 2
-#define VMWGFX_DRIVER_MINOR 11
+#define VMWGFX_DRIVER_MINOR 12
 #define VMWGFX_DRIVER_PATCHLEVEL 0
 #define VMWGFX_FILE_PAGE_OFFSET 0x00100000
 #define VMWGFX_FIFO_STATIC_SIZE (1024*1024)
--

2.9.3

Quoted 6 lines
Quoted 4 lines

_______________________________________________
dri-devel mailing list
[email protected]
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.freedesktop.org_mailman_listinfo_dri-2Ddevel&d=DwIBaQ&c=uilaK90D4TOVoH58JNXRgQ&r=wnSlgOCqfpNS4d02vP68_E9q2BNMCwfD2OZ_6dCFVQQ&m=vcENuMKTrk3-3q3adLKH-tLLJ7_eylT6C8xYUvaz4Uk&s=szfE_BhH3uP4zYt6YMTQfwYcndmHEXxRKrrja54qdG4&e=

_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel

#5 lore raw
Quoted 11 lines · Thomas Hellstrom
Quoted 10 lines · Daniel Vetter
Quoted 8 lines · Thomas Hellstrom

vmware tools has a daemon that gets layout information from the GUI and forwards it to DRM so that the modesetting code can set preferred connector locations and modes. This daemon was using control nodes but since control nodes were just removed, make it possible for the daemon to use render- or primary nodes instead. This is a bit ugly but will allow drm to proceed with removal of the mostly unused control-node code and allow vmware to proceed with fixing up automatic layout settings for gnome-shell/wayland.

Quoted 7 lines
Quoted 5 lines
Quoted 4 lines

We bump minor to inform user-space about the api change.

Seems reasonable.

So is this an Acked-by?

Sure.

Quoted 7 lines
Quoted 6 lines

I guess with hindsight we probably should have added
a virtual_x/y hint, similar to the hotpsot hinting we do for cursors. But since vmwgfx is the only virtual gpu that seems to do multi-screen that need was never all that apparent. I think we should fix that if/when vmwgfx switches over to atomic, atomic is super easy to extend.

Quoted 6 lines

Yes. I think we're open to a way to make this fit into the atomic infrastructure. We should remember though that other virtual GPUs may get this information from the virtual device rather than from user-space. The reason the information still originates from user-space in the VMware environment is the need to support remote screen layouts from a guest.

Well not so much standardize it for atomic, but as a property. The upshot with atomic is simply that then the atomic core can decode the value and stuff it into drm_crtc_state for you, which seems to help a lot with standardizing it across drivers. If this is purely vmwgfx specific, then I guess we can leave it as-is, but my experience has been that these modeset special cases tend to not stay special forever.

And now that I'm back from travelling and can look at things properly, we already have the standardized suggested_y/x/_property stuff, so for atomic I'd say definitely worth it to standardize this a bit. Maybe we need something like drm configuration properties, which are by default read-only, but can be written through sysfs? That way anyone could write them, as long as they can get at sysfs. And sysfs sounds like the more appropriate place to handle configuration stuff compared to some device ioctl. vmwgfx is probably not the only device that would need something like this, could be worth to standardize it a bit.

Quoted 8 lines
Quoted 3 lines

Also, with this patch I think we can restore backwards compat
by registering the render node as controlD (but only for vmwgfx, we'll keep the fake symlink for everyone else).

Actually, given that the feature was pulled out of the openSuSE and Fedora packages at the very last minute, it seems like we can skip the special VMware control node setup. The damage will be limited to within VMware.

Awesome, if we can avoid baking in drm_control as abi for the next 10 years I'll be very happy. Thanks a lot for this quick change of plans on your side.

Cheers, Daniel

Signature · 7 lines
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
#6 lore raw
Quoted 40 lines · Daniel Vetter
Quoted 11 lines · Thomas Hellstrom
Quoted 10 lines · Daniel Vetter
Quoted 8 lines · Thomas Hellstrom

vmware tools has a daemon that gets layout information from the GUI and forwards it to DRM so that the modesetting code can set preferred connector locations and modes. This daemon was using control nodes but since control nodes were just removed, make it possible for the daemon to use render- or primary nodes instead. This is a bit ugly but will allow drm to proceed with removal of the mostly unused control-node code and allow vmware to proceed with fixing up automatic layout settings for gnome-shell/wayland.

Quoted 6 lines
Quoted 5 lines
Quoted 4 lines

We bump minor to inform user-space about the api change.

Seems reasonable.

So is this an Acked-by?

Sure.

Quoted 6 lines
Quoted 6 lines

I guess with hindsight we probably should have added
a virtual_x/y hint, similar to the hotpsot hinting we do for cursors. But since vmwgfx is the only virtual gpu that seems to do multi-screen that need was never all that apparent. I think we should fix that if/when vmwgfx switches over to atomic, atomic is super easy to extend.

Quoted 6 lines

Yes. I think we're open to a way to make this fit into the atomic infrastructure. We should remember though that other virtual GPUs may get this information from the virtual device rather than from user-space. The reason the information still originates from user-space in the VMware environment is the need to support remote screen layouts from a guest.

Well not so much standardize it for atomic, but as a property. The upshot with atomic is simply that then the atomic core can decode the value and stuff it into drm_crtc_state for you, which seems to help a lot with standardizing it across drivers. If this is purely vmwgfx specific, then I guess we can leave it as-is, but my experience has been that these modeset special cases tend to not stay special forever.

Quoted 9 lines

And now that I'm back from travelling and can look at things properly, we already have the standardized suggested_y/x/_property stuff, so for atomic I'd say definitely worth it to standardize this a bit. Maybe we need something like drm configuration properties, which are by default read-only, but can be written through sysfs? That way anyone could write them, as long as they can get at sysfs. And sysfs sounds like the more appropriate place to handle configuration stuff compared to some device ioctl. vmwgfx is probably not the only device that would need something like this, could be worth to standardize it a bit.

Sure.

Quoted 8 lines
Quoted 8 lines
Quoted 4 lines

Also, with this patch I think we can restore backwards compat
by registering the render node as controlD (but only for vmwgfx, we'll keep the fake symlink for everyone else).

Actually, given that the feature was pulled out of the openSuSE and Fedora packages at the very last minute, it seems like we can skip the special VMware control node setup. The damage will be limited to within VMware.

Quoted 5 lines

Awesome, if we can avoid baking in drm_control as abi for the next 10 years I'll be very happy. Thanks a lot for this quick change of plans on your side.

Cheers, Daniel

Thanks. Your work cleaning up DRM is very much appreciated. We don't want to get in the way if avoidable.

/Thomas

_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel