All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Bisson <gary.bisson@boundarydevices.com>
To: Tom Hochstein <tom.hochstein@nxp.com>
Cc: meta-freescale Mailing List <meta-freescale@yoctoproject.org>,
	Yuqing Zhu <carol.zhu@nxp.com>
Subject: Re: [PATCH 0/2] Fix Hantro/Gstreamer build issues
Date: Wed, 3 Oct 2018 16:19:25 +0200	[thread overview]
Message-ID: <CAAMH-yu1aNMhYMRpNS=tyksYZgakeLfjiRZ3X6ZBhQT5B5it3Q@mail.gmail.com> (raw)
In-Reply-To: <VI1PR04MB524795387BBEAA8139C84B8BE2E90@VI1PR04MB5247.eurprd04.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]

Hi Tom,

On Wed, Oct 3, 2018 at 3:50 PM Tom Hochstein <tom.hochstein@nxp.com> wrote:

> Hi Gary,
>
> Thanks for this fix and for letting us know about the ownership mistake.
>
> Related to this, I am working on a dedicated linux-imx-headers recipe with
> Otavio. With such a recipe, do you see a problem with copying ion.h from
> drivers/staging/android to /usr/include/linux?
>

Where do you plan on installing those headers? They shouldn't be mixed with
the libc/toolchain headers.

Then I'm not sure to see the benefit of such linux-imx-headers recipe vs.
pointing to the kernel dir as you do it already for many packages:
$ grep -r STAGING_KERNEL_ recipes-{bsp,multimedia} | wc -l
20
$ grep -r STAGING_KERNEL_ recipes-{bsp,multimedia} | sed 's/:.*//' | uniq
recipes-bsp/imx-vpu/imx-vpu_5.4.38.bb
recipes-bsp/imx-test/imx-test_git.bb
recipes-bsp/imx-vpu-hantro/imx-vpu-hantro_1.8.0.bb
recipes-bsp/imx-lib/imx-lib_git.bb
recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.14.imx.bb
recipes-multimedia/gstreamer/gstreamer1.0-plugins-imx_git.bb
recipes-multimedia/gstreamer/imx-gst1.0-plugin_4.4.2.bb
recipes-multimedia/alsa/imx-alsa-plugins_1.0.26.bb

Regards,
Gary

[-- Attachment #2: Type: text/html, Size: 2138 bytes --]

  reply	other threads:[~2018-10-03 14:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-03 10:24 [PATCH 0/2] Fix Hantro/Gstreamer build issues Gary Bisson
2018-10-03 10:24 ` [PATCH 1/2] imx-vpu-hantro: fix build issue Gary Bisson
2018-10-03 13:03   ` Carlos Rafael Giani
2018-10-04 15:47     ` Otavio Salvador
2018-10-04 19:49       ` Carlos Rafael Giani
2018-10-05 13:32         ` Otavio Salvador
2018-10-03 10:24 ` [PATCH 2/2] gstreamer1.0-plugins-base: " Gary Bisson
2018-10-03 13:50 ` [PATCH 0/2] Fix Hantro/Gstreamer build issues Tom Hochstein
2018-10-03 14:19   ` Gary Bisson [this message]
2018-10-03 18:43   ` Otavio Salvador
2018-10-03 18:47     ` Tom Hochstein
2018-10-03 18:50       ` Otavio Salvador
2018-10-05 12:09         ` Carlos Rafael Giani

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='CAAMH-yu1aNMhYMRpNS=tyksYZgakeLfjiRZ3X6ZBhQT5B5it3Q@mail.gmail.com' \
    --to=gary.bisson@boundarydevices.com \
    --cc=carol.zhu@nxp.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=tom.hochstein@nxp.com \
    /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.