Commits on Source (18)
-
Jeremy Huddleston Sequoia authored
Signed-off-by:
Jeremy Huddleston Sequoia <jeremyhu@apple.com>
-
Jeremy Huddleston Sequoia authored
Signed-off-by:
Jeremy Huddleston Sequoia <jeremyhu@apple.com>
-
Jeremy Huddleston Sequoia authored
rootless: Ensure gResizeDeathPix is stored in locally-managed memory rather than re-using the implementation's backing store The implementation owns the pointer during RootlessStopDrawing and RootlessStartDrawing and is free to (does) change it. Rootless cannot assume ownership of this memory region. This is possibly the cause of some hard to diagnose crashes in XQuartz over the years. Signed-off-by:
Jeremy Huddleston Sequoia <jeremyhu@apple.com>
-
Jeremy Huddleston Sequoia authored
If none of the four corners is fixed, we can use RL_GRAVITY_NORTH_WEST weighting for the operation to let the implementation presetve the window bits for us. Signed-off-by:
Jeremy Huddleston Sequoia <jeremyhu@apple.com>
-
Jeremy Huddleston Sequoia authored
I don't see a reason why we would want to preserve pixels that are going to not be visible anyways. The rootless implementation already handles preserving the relevant bits for us. Signed-off-by:
Jeremy Huddleston Sequoia <jeremyhu@apple.com>
-
Jeremy Huddleston Sequoia authored
Signed-off-by:
Jeremy Huddleston Sequoia <jeremyhu@apple.com>
-
Jeremy Huddleston Sequoia authored
rootless: Remove an unnecessary memory copy when handling resize with gravity RL_GRAVITY_NONE (border width changes) This should no longer be necessary since we only support implementations that handle preserving the bits across resize Signed-off-by:
Jeremy Huddleston Sequoia <jeremyhu@apple.com>
-
Jeremy Huddleston Sequoia authored
This should no longer be necessary since we only support implementations that handle preserving the bits across resize. We can use RootlessNoCopyWindow instead. Signed-off-by:
Jeremy Huddleston Sequoia <jeremyhu@apple.com>
-
Jeremy Huddleston Sequoia authored
This updates rootless to treat pixmaps consistently with COMPOSITE, using the screen_x and screen_y values rather than doing hacky math. This will allow for proper bounds checking on a given PixmapRec. Signed-off-by:
Jeremy Huddleston Sequoia <jeremyhu@apple.com>
-
This creates xwl_add_format_and_mod_to_list, which is a helper that adds a format/mod combo to a xwl_format* list. This will be used by both the modifier event handling and the tranche format handling. Reviewed-by:
Michel Dänzer <mdaenzer@redhat.com>
-
Reviewed-by:
Michel Dänzer <mdaenzer@redhat.com> [ Michel Dänzer: * Sort protocol #includes lexically. * memcpy to &xwl_feedback->main_dev directly in xwl_dmabuf_feedback_main_device. ]
-
Reviewed-by:
Michel Dänzer <mdaenzer@redhat.com>
-
This reads from the format list, which is not yet filled in. Reviewed-by:
Michel Dänzer <mdaenzer@redhat.com>
-
This adds xwl_get_formats Reviewed-by:
Michel Dänzer <mdaenzer@redhat.com> [ Michel Dänzer: * Remove unused variable i from xwl_glamor_get_formats ]
-
If protocol version 4 of linux_dmabuf is in use, then the compositor may not return anything with the modifiers event. We instead will return the formats/mods reported for the main device. Reviewed-by:
Michel Dänzer <mdaenzer@redhat.com> [ Michel Dänzer: * Move main_dev declaration to where it's used in xwl_glamor_get_formats * Add empty line between variable declaration and comment ]
-
This adds to xwl_glamor_is_modifier_supported, where if feedback is in use we will check that the format/mod is allowed in any device advertised by the compositor. Reviewed-by:
Michel Dänzer <mdaenzer@redhat.com> [ Michel Dänzer: * Move dev_formats declaration to where it's used in xwl_feedback_is_modifier_supported * Add curly braces around multi-line statement in xwl_glamor_is_modifier_supported ]
-
In dri3_get_supported_modifiers we were previously intersecting the drawable mods and the screen mods. This meant all screen mods were returned, but the ones compatible with the drawable were returned in the drawable mods list and the rest are returned in the screen mods list. This is a problem with linux_dmabuf v4 since the drawable mods may contain different mods not found in the screen mods (such as scanout entries). This change removes the intersection, and just returns the drawable/screen mod lists directly. Reviewed-by:
Michel Dänzer <mdaenzer@redhat.com>
-
If the dmabuf protocol's feedback object gave us a new list of modifiers, send PresentCompleteModeSuboptimalCopy to the client to inform them that they need to call GetSupportedModifiers. Reviewed-by:
Michel Dänzer <mdaenzer@redhat.com>
Showing
- dix/dispatch.c 1 addition, 1 deletiondix/dispatch.c
- dri3/dri3_screen.c 12 additions, 44 deletionsdri3/dri3_screen.c
- exa/exa.c 1 addition, 1 deletionexa/exa.c
- exa/exa_accel.c 1 addition, 1 deletionexa/exa_accel.c
- fb/fb.h 1 addition, 1 deletionfb/fb.h
- fb/fbpixmap.c 1 addition, 1 deletionfb/fbpixmap.c
- fb/fbwindow.c 1 addition, 1 deletionfb/fbwindow.c
- glamor/glamor_copy.c 1 addition, 1 deletionglamor/glamor_copy.c
- glamor/glamor_pixmap.c 1 addition, 1 deletionglamor/glamor_pixmap.c
- hw/xwayland/xwayland-glamor-eglstream.c 2 additions, 1 deletionhw/xwayland/xwayland-glamor-eglstream.c
- hw/xwayland/xwayland-glamor-gbm.c 18 additions, 1 deletionhw/xwayland/xwayland-glamor-gbm.c
- hw/xwayland/xwayland-glamor.c 474 additions, 49 deletionshw/xwayland/xwayland-glamor.c
- hw/xwayland/xwayland-glamor.h 8 additions, 0 deletionshw/xwayland/xwayland-glamor.h
- hw/xwayland/xwayland-present.c 28 additions, 1 deletionhw/xwayland/xwayland-present.c
- hw/xwayland/xwayland-screen.c 2 additions, 0 deletionshw/xwayland/xwayland-screen.c
- hw/xwayland/xwayland-screen.h 3 additions, 0 deletionshw/xwayland/xwayland-screen.h
- hw/xwayland/xwayland-window.c 48 additions, 0 deletionshw/xwayland/xwayland-window.c
- hw/xwayland/xwayland-window.h 51 additions, 0 deletionshw/xwayland/xwayland-window.h
- include/pixmapstr.h 1 addition, 1 deletioninclude/pixmapstr.h
- mi/miexpose.c 1 addition, 1 deletionmi/miexpose.c
This diff is collapsed.