From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2, 1/1] libv4l: add an option for IR BPF based decoders
Date: Fri, 9 Nov 2018 21:54:04 +0100 [thread overview]
Message-ID: <20181109215404.345454ec@windsurf> (raw)
In-Reply-To: <20181109172648.10289-1-fontaine.fabrice@gmail.com>
Hello,
On Fri, 9 Nov 2018 18:26:48 +0100, Fabrice Fontaine wrote:
> Bump to version 1.61.1 added BPF based protocols support:
> https://git.linuxtv.org/v4l-utils.git/commit/?id=d6025b0e8c7f57b0f9390f987acc5eed57360d80
>
> However, this dependency needs BPF support in kernel. On old kernels
> (before 3.18), __NR_BPF is not defined for all architectures.
> So retrieve upstream patch and add an option to enable BPF only if
> headers are above 3.18.
>
> Also drop patch to add bpf_common.h on old kernels (not needed anymore)
>
> Fixes:
> - http://autobuild.buildroot.org/results/442de57cb76a7b38d71d690490faadc641036374
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Thanks for working on this!
> +ifeq ($(BR2_PACKAGE_LIBV4L_UTILS_IR_BPF_BASED_DECODERS),y)
> +LIBV4L_CONF_OPTS += --enable-bpf
> +LIBV4L_DEPENDENCIES += elfutils
> +
> # Disable clang that is used to build BPF (in-kernel bytecode machine) protocols
> LIBV4L_CONF_ENV += ac_cv_prog_CLANG=""
So without clang, how are BPF protocols being built ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-11-09 20:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 17:26 [Buildroot] [PATCH v2, 1/1] libv4l: add an option for IR BPF based decoders Fabrice Fontaine
2018-11-09 20:54 ` Thomas Petazzoni [this message]
2018-11-09 21:30 ` Peter Seiderer
2019-08-01 10:43 ` Arnout Vandecappelle
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=20181109215404.345454ec@windsurf \
--to=thomas.petazzoni@bootlin.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