xlat: workaround V4L2_CID_USER_IMX_BASE Linux kernel ABI breakage
authorDmitry V. Levin <ldv@altlinux.org>
Sat, 18 Aug 2018 07:22:47 +0000 (07:22 +0000)
committerDmitry V. Levin <ldv@altlinux.org>
Sun, 19 Aug 2018 10:26:18 +0000 (10:26 +0000)
commitb89a69dec27cf638df0e17db80ed937c3e1abf77
treefdcba6cc798c140d85978598048fd033c13a488a
parenta264eb3b65e963cff69169d865c48b1465c1abc6
xlat: workaround V4L2_CID_USER_IMX_BASE Linux kernel ABI breakage

Linux kernel commit v4.18-rc2-106-g421860b9d47053badce4b247576fa48df9ab4c48
has changed the value of V4L2_CID_USER_IMX_BASE constant introduced
by commit v4.13-rc1~141^2~121 because the old value was already used
by V4L2_CID_USER_MAX217X_BASE.

This is of course an ABI breakage that affects Linux kernels starting
with 4.13 and up to 4.18, as well as their LTS derivatives.

Since the imx driver didn't provide any public control ID definitions,
it looks like the best way to handle this situation is to pretend that
the old value of V4L2_CID_USER_IMX_BASE didn't exist.

* xlat/v4l2_control_id_bases.in (V4L2_CID_USER_IMX_BASE): Redefine.

Co-Authored-by: Eugene Syromyatnikov <evgsyr@gmail.com>
xlat/v4l2_control_id_bases.in