From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id B3828E00ADD; Wed, 3 Oct 2018 07:19:37 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, HTML_MESSAGE, RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no * trust * [209.85.160.177 listed in list.dnswl.org] * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * 0.0 HTML_MESSAGE BODY: HTML included in message Received: from mail-qt1-f177.google.com (mail-qt1-f177.google.com [209.85.160.177]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 02518E0097D for ; Wed, 3 Oct 2018 07:19:36 -0700 (PDT) Received: by mail-qt1-f177.google.com with SMTP id u34-v6so6074856qth.3 for ; Wed, 03 Oct 2018 07:19:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boundarydevices-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=D41pIu9g/B5tO5ykb562Serep1pYy4BCzRm8YY2mSpg=; b=vN/mLxDYPsVb2pq81XyYB8gA52qx1SVzNQzwlG4dFG0JbwElZ3SH34Zd15hYxrNCRY taxU18gOixaS5d5NXBxM1axQXjmBM2qb5V+GO1DWeWNYfCcQGEVLDv4jD1DBpsr9mjOF BqKGsZprZf2vu+QRd3/XOkR6Sx4aYpT2DBjNYUJADnaKTpxl1iYVCvwSlREzqYyXmlEy QpzPNdEtUO8PDEwvFizFaVtWAURB8Ys8rYf9egkpE5sndhkjhEf7q2f1dcAuegwcT69x eB7gzhn2+1GAx3HhMjwlc3l4vpDQBUiWI9eDqaoDO5Aeu4HEzdGTWCCmS5xiKV/CtNBF KpBQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=D41pIu9g/B5tO5ykb562Serep1pYy4BCzRm8YY2mSpg=; b=oJ8gs1dx6FzSDnvxZbZEqSospSp29B/PKsVoN9HjYCEPv8+++ynrnRV2a88Pcp49CD pFikXdqqsWVgYafpPR8JjcqyWktCAGIJ8xZPd1Vkqf+wuE2CUsM9ds7t/e9eQSHPeM7A yuV5DfdDQPYGd+k9h3jr3BCUy/8sSJwAgHGzjDKQJwFeCY46d0Ckc9vCNb4Gi5f+G1L6 4nxLkIrQV0Wb6jEsOJY1rYt1+z8OR2dVke3+CmuCHutfFmuMpvFngUfDVn74bUI0v6Jz jt8C1z0MrRnXmx9tP9m0aDLgb53fFrLBOUOatnHasGy2BlRiCtTjs4drMJJIXbwSHMMM 1LLw== X-Gm-Message-State: ABuFfogbLy18g+VCIP1CPmmnC0VKOOzmurBykr5O2NdmIHUVLOGb7n9l s8vIzcOa9o2b5WvFCG3elBiGc0uPUAnxD4caCp2Mqg== X-Google-Smtp-Source: ACcGV63jQtgn+77La+N8XuPlZNP5o/JNFkfHLXTy5/k1s4hLHIanYr9yVie3QBEKiPftO4MEx5JV3Sm+EpVwBUEnfyM= X-Received: by 2002:ac8:5394:: with SMTP id x20-v6mr1352459qtp.146.1538576376272; Wed, 03 Oct 2018 07:19:36 -0700 (PDT) MIME-Version: 1.0 References: <20181003102443.29749-1-gary.bisson@boundarydevices.com> In-Reply-To: From: Gary Bisson Date: Wed, 3 Oct 2018 16:19:25 +0200 Message-ID: To: Tom Hochstein Cc: meta-freescale Mailing List , Yuqing Zhu Subject: Re: [PATCH 0/2] Fix Hantro/Gstreamer build issues X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Oct 2018 14:19:37 -0000 Content-Type: multipart/alternative; boundary="0000000000005e2b7a057753ba82" --0000000000005e2b7a057753ba82 Content-Type: text/plain; charset="UTF-8" Hi Tom, On Wed, Oct 3, 2018 at 3:50 PM Tom Hochstein 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 --0000000000005e2b7a057753ba82 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Tom,

On We= d, 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 dr= ivers/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-h= antro/imx-vpu-hantro_1.8.0.bb
recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.14.imx.bb
recipes-multimedia/gstreamer/gstreamer1.0-plugins-imx_git.bb
recipes-multimed= ia/gstreamer/imx-gst1.0-plugi= n_4.4.2.bb
recipes-multimedia/alsa/imx-alsa-plugins_1.0.26.bb

Regards,
Gary

=
--0000000000005e2b7a057753ba82--