diff options
| author | Eric Anholt <[email protected]> | 2020-04-21 09:21:52 -0700 |
|---|---|---|
| committer | Marge Bot <[email protected]> | 2020-04-23 17:54:54 +0000 |
| commit | e9add0c501c3765cae43ef60ec58404c2340991b (patch) | |
| tree | 31887ec82b6531e5dc8e9d4ca1e6144af9e2a0ee /src/broadcom | |
| parent | 5a8718f01b3976e1bc82362a907befef68a7f525 (diff) | |
drm-shim: Let the driver choose to overwrite the first render node.
When I was writing drm-shim, I was focused on the v3d kmsro case -- use my
intel device as the kmsro display device and add on a simulator-based v3d
device that we could render with. But for the noop backends we use for
shader-db, it's a lot more useful to just overwrite the first render node
in the system so that you don't have to pass a -d <how many render nodes I
already have in my system> argument.
Reviewed-by: Lionel Landwerlin <[email protected]>
Reviewed-by: Iago Toral Quiroga <[email protected]>
Reviewed-by: Christian Gmeiner <[email protected]>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4664>
Diffstat (limited to 'src/broadcom')
| -rw-r--r-- | src/broadcom/drm-shim/v3d.c | 2 | ||||
| -rw-r--r-- | src/broadcom/drm-shim/v3d_noop.c | 2 |
2 files changed, 4 insertions, 0 deletions
diff --git a/src/broadcom/drm-shim/v3d.c b/src/broadcom/drm-shim/v3d.c index 81e34c128e2..f4d5bd31323 100644 --- a/src/broadcom/drm-shim/v3d.c +++ b/src/broadcom/drm-shim/v3d.c @@ -28,6 +28,8 @@ #include "v3d.h" #include "v3d_simulator_wrapper.h" +bool drm_shim_driver_prefers_first_render_node = false; + static struct v3d_device_info devinfo; struct v3d_shim_device v3d = { .devinfo = &devinfo diff --git a/src/broadcom/drm-shim/v3d_noop.c b/src/broadcom/drm-shim/v3d_noop.c index 3caa757bb3e..fd92e8859c5 100644 --- a/src/broadcom/drm-shim/v3d_noop.c +++ b/src/broadcom/drm-shim/v3d_noop.c @@ -28,6 +28,8 @@ #include "drm-uapi/v3d_drm.h" #include "drm-shim/drm_shim.h" +bool drm_shim_driver_prefers_first_render_node = true; + struct v3d_bo { struct shim_bo base; uint32_t offset; |