summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2019-11-02 17:52:13 +0100
committerwm4 <wm4@nowhere>2019-11-02 17:52:13 +0100
commit20c1bd8a5e0bdddab016363489406220ce415128 (patch)
tree92c1cb49aa6db6582816fa9dcdc449b1d879ce4f
parente58e650a97a3938baeb7d8bb62cdae04ac6b6fb1 (diff)
downloadmpv-20c1bd8a5e0bdddab016363489406220ce415128.tar.bz2
mpv-20c1bd8a5e0bdddab016363489406220ce415128.tar.xz
zimg: correct RGB30 order (probably)
According to the definition of the GL format, and the definition in img_format.h, and the actual output by vo_gpu, the order of components was probably wrong. It's exceedingly likely that the vo_drm format (for which this was originally written) has the same layout, so this was probably a bug from when the zimg wrapper code was refactored.
-rw-r--r--video/zimg.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/video/zimg.c b/video/zimg.c
index 7010630e7a..94bd241c96 100644
--- a/video/zimg.c
+++ b/video/zimg.c
@@ -293,7 +293,7 @@ PA_WORD_3(pa_ccc8z8, uint32_t, uint8_t, 0, 8, 16, 0)
UN_WORD_3(un_x8ccc8, uint32_t, uint8_t, 8, 16, 24, 0xFFu)
PA_WORD_3(pa_z8ccc8, uint32_t, uint8_t, 8, 16, 24, 0)
UN_WORD_3(un_ccc10x2, uint32_t, uint16_t, 0, 10, 20, 0x3FFu)
-PA_WORD_3(pa_ccc10z2, uint32_t, uint16_t, 0, 10, 20, 0)
+PA_WORD_3(pa_ccc10z2, uint32_t, uint16_t, 20, 10, 0, 0)
#define PA_WORD_2(name, packed_t, plane_t, sh_c0, sh_c1, pad) \
static void name(void *dst, void *src[], int x0, int x1) { \