From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/2] gst-fsl-plugins: requires kernel headers <= 3.10 (branch yem/quickies)
Date: Sat, 26 Jul 2014 00:32:03 +0200 [thread overview]
Message-ID: <20140726003203.355212eb@free-electrons.com> (raw)
In-Reply-To: <cover.1406323367.git.yann.morin.1998@free.fr>
Dear Yann E. MORIN,
On Fri, 25 Jul 2014 23:28:11 +0200, Yann E. MORIN wrote:
> As reported by Gary, gst-fsl-plugins use part of the v4l2 API that was
> removed in linux 3.11, so it should not be made available for toolchains
> with kernel headers >= 3.11, but only for headers <= 3.10.
That's kind of odd. Isn't the kernel to userspace API supposed to
remain backward compatible? Isn't this rather a story of custom v4l2
APIs added by Freescale but never mainlined?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-07-25 22:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 21:28 [Buildroot] [PATCH 0/2] gst-fsl-plugins: requires kernel headers <= 3.10 (branch yem/quickies) Yann E. MORIN
2014-07-25 21:28 ` [Buildroot] [PATCH 1/2] docs/manual: enhance doc for BR2_TOOLCHAIN_HEADERS_AT_LEAST_X_Y Yann E. MORIN
2014-07-26 18:25 ` Thomas De Schampheleire
2014-07-27 12:34 ` Thomas Petazzoni
2014-07-27 12:49 ` Yann E. MORIN
2014-07-27 13:04 ` Thomas Petazzoni
2014-07-27 13:08 ` Thomas Petazzoni
2014-07-25 21:28 ` [Buildroot] [PATCH 2/2] package/gst-fsl-plugins: not available for kernel headers >= 3.11 Yann E. MORIN
2014-07-25 22:32 ` Thomas Petazzoni [this message]
2014-07-25 23:21 ` [Buildroot] [PATCH 0/2] gst-fsl-plugins: requires kernel headers <= 3.10 (branch yem/quickies) Gary Bisson
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=20140726003203.355212eb@free-electrons.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.