diff options
| author | Vito Caputo <vcaputo@pengaru.com> | 2022-05-23 21:48:13 -0700 |
|---|---|---|
| committer | Vito Caputo <vcaputo@pengaru.com> | 2022-05-23 22:55:56 -0700 |
| commit | f1c36777bdf0464129e8c2e00bb9339868376043 (patch) | |
| tree | f906096bb72dfc64d27c91e11bb8e26effc649a5 | |
| parent | 4268d43b2dac01c354409a0d5dbbbe903d6e28d0 (diff) | |
modules/compose: don't clear frame in prepare_frame()
I'm not sure why this was being done, it was probably just
vestigial from whatever I bootstrapped the compose module with
and never thought to remove it.
The first compose layer rendered will clear the frame if
necessary. By compose doing it ahead of time, it's performing
potentially unnecessary work clearing if the first layer is a
frame-filler style render where no clear is ever performed.
| -rw-r--r-- | src/modules/compose/compose.c | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/src/modules/compose/compose.c b/src/modules/compose/compose.c index f55e516..bdd4b70 100644 --- a/src/modules/compose/compose.c +++ b/src/modules/compose/compose.c @@ -130,8 +130,6 @@ static void compose_prepare_frame(void *context, unsigned ticks, unsigned n_cpus { compose_context_t *ctxt = context; - til_fb_fragment_clear(fragment); - if (ctxt->texture.module) { if (!ctxt->texture_fb.buf || ctxt->texture_fb.frame_width != fragment->frame_width || |