On 25/01/17 14:42, Christian König wrote: > From: Christian König <christian.koe...@amd.com> > > Most likely only partially correct, but at least a start. > > Signed-off-by: Christian König <christian.koe...@amd.com> > --- > src/gallium/state_trackers/va/config.c | 9 ++++++--- > src/gallium/state_trackers/va/image.c | 10 ++++++++++ > src/gallium/state_trackers/va/surface.c | 28 ++++++++++++++-------------- > src/gallium/state_trackers/va/va_private.h | 3 ++- > 4 files changed, 32 insertions(+), 18 deletions(-)
Is there a reason why this is using P016 for 10-bit surfaces rather than P010? I know they are really the same, but the existing VAAPI 10-bit implementation (Intel for Apollo Lake / Kaby Lake) has P010 as the format rather than P016 with implicitly ignored low bits. (As long as all of the query functions return the right formats then I don't actually mind, but it probably does increase confusion for users.) Thanks, - Mark _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
