From: Otavio Salvador <otavio.salvador@ossystems.com.br>
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 15:50:56 -0300 [thread overview]
Message-ID: <CAP9ODKoB8ov1u0sQxp_peAnev8e2SbD976Ky5owNhC_93gfZuQ@mail.gmail.com> (raw)
In-Reply-To: <VI1PR04MB524795643F8AF9393E38252CE2E90@VI1PR04MB5247.eurprd04.prod.outlook.com>
On Wed, Oct 3, 2018 at 3:47 PM Tom Hochstein <tom.hochstein@nxp.com> wrote:
> > /usr/include/imx/linux
>
> For new headers, is there a reason why we can't just install to /usr/include/linux? Will be much nicer than having to modify source code.
Yes; we must know what is specific of i.MX. The best way to fix it is
upstreaming it to mainline Linux and get rid of forked headers ;-)
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750
next prev parent reply other threads:[~2018-10-03 18:51 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
2018-10-03 18:43 ` Otavio Salvador
2018-10-03 18:47 ` Tom Hochstein
2018-10-03 18:50 ` Otavio Salvador [this message]
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=CAP9ODKoB8ov1u0sQxp_peAnev8e2SbD976Ky5owNhC_93gfZuQ@mail.gmail.com \
--to=otavio.salvador@ossystems.com.br \
--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.