Bug#1010817: Ambiguity between intel-media-va-driver and i965-va-driver descriptions

[Nicholas D Steeves <sten@debian.org>]

Package: i965-va-driver
Version: 2.4.1+dfsg1-1
Severity: normal
X-Debbugs-Cc: Sebastian Ramacher <sramacher@debian.org>, debian-backports@lists.debian.org
Control: affects -1 intel-media-va-driver

Hi Sebastien,

I noticed that it is unclear whether a user on Broadwell to Cannon Lake should choose i965-va-driver or intel-media-va-driver.

i965-va-driver Description:
…
  * Haswell
  * Broadwell
  * Skylake
  * Kaby Lake
  * Coffee Lake
  * Cannon Lake

intel-media-va-driver Description:
…
 platforms include:
  * Broadwell
  * Skylake
  * Broxton
  * Apollo Lake
  * Kaby Lake
  * Coffee Lake
  * Whiskey Lake
  * Cannon Lake
  * Ice Lake

If intel-media-va-driver provides a better experience for users of this generation of hardware, then i965-va-driver should be annotated to read something like:
…
  * Haswell
  * Broadwell (supported, but prefer the use of intel-media-va-driver)
  * Skylake (supported, but prefer the use of intel-media-va-driver)
  * Kaby Lake (supported, but prefer the use of intel-media-va-driver)
  * Coffee Lake (supported, but prefer the use of intel-media-va-driver)
  * Cannon Lake (supported, but prefer the use of intel-media-va-driver)

I suspect that the above is probably the correct course of action, because I read (upstream, IIRC) that intel-media-va-driver allegedly provides support for a wider variety of codecs.

If support for these generations of hardware isn't great in intel-media-va-driver, then intel-media-va-driver should be annotated with the inverse.

This might arguably be a bit pedantic, because va-driver-all installs both, and I would assume that the best choice is automatically chosen (change annotation to this effect if it's the case)...I'm not sure if that's the case though.  Were it the case, the proposed revision would be useful for users who haven't installed va-driver-all for whatever reasons.

Thanks,
Nicholas