From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/ffmpeg: disable build of nvidia hardware acceleration support
Date: Sat, 22 Jul 2017 21:39:18 +0200 [thread overview]
Message-ID: <20170722213918.30c3f282@windsurf> (raw)
In-Reply-To: <20170722151306.22870-1-bernd.kuhls@t-online.de>
Hello,
On Sat, 22 Jul 2017 17:13:06 +0200, Bernd Kuhls wrote:
> ffmpeg always enables support for nvenc/cuda even if their support
> libraries are not present:
>
> External libraries providing hardware acceleration:
> cuda cuvid nvenc
> [...]
> Enabled hwaccels:
> h264_cuvid mjpeg_cuvid mpeg2_cuvid vc1_cuvid vp9_cuvid
> hevc_cuvid mpeg1_cuvid mpeg4_cuvid vp8_cuvid
>
> This leads to a crash in freeswitch git master when transcoding video
> streams on a system without nvidia hardware:
>
> 2017-07-22 15:06:27.306760 [INFO] avcodec.c:1077 initializing encoder 352x288
> 2017-07-22 15:06:27.306760 [NOTICE] avcodec.c:828 NVENC HW CODEC ENABLED
>
> This patch disables the support of nvidia hardware acceleration support
> for now until the needed packages are added to buildroot. For details
> about this please refer to https://developer.nvidia.com/ffmpeg
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> package/ffmpeg/ffmpeg.mk | 3 +++
> 1 file changed, 3 insertions(+)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-07-22 19:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-22 15:13 [Buildroot] [PATCH 1/1] package/ffmpeg: disable build of nvidia hardware acceleration support Bernd Kuhls
2017-07-22 19:39 ` Thomas Petazzoni [this message]
2017-07-25 22:10 ` Peter Korsgaard
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=20170722213918.30c3f282@windsurf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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