From: tm512 <tm512@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: nv-codec-header: update to 12.1.14.0.
Date: Tue, 17 Oct 2023 22:55:15 +0200 [thread overview]
Message-ID: <20231017205515.OUxphPXFDLR42fg1FeOu0x6_-brA8ao-8tcOzadYED4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44781@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 726 bytes --]
New comment by tm512 on void-packages repository
https://github.com/void-linux/void-packages/pull/44781#issuecomment-1767165246
Comment:
Thanks for the clarification, sounds like 12.x is a necessary upgrade then. It was just something I noticed before finding your PR, I went to update nv-codec-headers to get NVENC working on a `release/6.0` branch build of ffmpeg for my own use, and noticed that 11.1.5.3 retained support for older drivers and was enough to satisfy ffmpeg 6.0, so I figured I would chime in. A repo maintainer would have to give input on whether it's worthwhile to split the package to retain the option for supporting `nvidia470` while that driver is around and ffmpeg still supports running with 11.x.
next prev parent reply other threads:[~2023-10-17 20:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 8:56 [PR PATCH] nv-codec-header: update to 12.0.16.0 dataCobra
2023-07-05 14:32 ` [PR PATCH] [Updated] " void-linux
2023-07-10 7:49 ` dataCobra
2023-07-10 18:04 ` dataCobra
2023-07-10 18:11 ` dataCobra
2023-07-15 8:37 ` dataCobra
2023-07-16 9:16 ` dataCobra
2023-07-21 5:15 ` dataCobra
2023-07-24 6:36 ` dataCobra
2023-10-05 15:42 ` dataCobra
2023-10-17 0:07 ` tm512
2023-10-17 12:00 ` dataCobra
2023-10-17 12:08 ` [PR PATCH] [Updated] " dataCobra
2023-10-17 20:55 ` tm512 [this message]
2023-11-08 14:15 ` [PR PATCH] [Updated] nv-codec-header: update to 12.1.14.0 dataCobra
2023-11-08 14:18 ` [PR PATCH] [Updated] nv-codec-header: update to 12.0.16.1 dataCobra
2024-02-07 1:44 ` github-actions
2024-02-07 14:09 ` [PR PATCH] [Updated] " dataCobra
2024-05-09 1:46 ` github-actions
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231017205515.OUxphPXFDLR42fg1FeOu0x6_-brA8ao-8tcOzadYED4@z \
--to=tm512@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).