Bug#1010817: marked as done (Ambiguity between intel-media-va-driver and i965-va-driver descriptions)
Your message dated Wed, 11 May 2022 08:20:31 +0200
with message-id <YntVrxG5jvHeVIfG@ramacher.at>
and subject line Re: Bug#1010817: Ambiguity between intel-media-va-driver and i965-va-driver descriptions
has caused the Debian Bug report #1010817,
regarding Ambiguity between intel-media-va-driver and i965-va-driver descriptions
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
1010817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010817
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
tags 1010817 wontfix
thanks
On 2022-05-10 15:22:52 -0400, Nicholas D Steeves wrote:
> 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.
I'm not a big fan of having this information in the Description. It is
bound to change over time (and it has). Instead of having some outdated
info on the better driver in the description, I think that
https://wiki.debian.org/HardwareVideoAcceleration is better place for
that.
Cheers
--
Sebastian Ramacher
--- End Message ---
Reply to: