From: Gary Thomas <gary@mlbassoc.com>
To: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: [meta-fsl-arm] Error in recent build
Date: Mon, 5 Oct 2015 15:18:54 -0600 [thread overview]
Message-ID: <5612E93E.2050908@mlbassoc.com> (raw)
I've updated my Poky/Yocto build to the latest master:
meta:eac61f37e36099f74485dab398b57f3812826d17
meta-fsl-arm:e76622d2b89952f817005ca0bf3575170aaaa7f9
I'm now getting this error:
|
/local/p0382-cutting-edge_2014-11-21/tmp/work/imx6qsabresd-amltd-linux-gnueabi/kernel-module-imx-gpu-viv/5.0.11.p7.1-r0/kernel-module-imx-gpu-viv-5.0.11.p7.1/kernel-module-imx-gpu-viv-src/hal/os/linux/kernel/platform/freescale/gc_hal_kernel_platform_imx6q14.c:78:32:
fatal error: linux/busfreq-imx6.h: No such file or directory
| #include <linux/busfreq-imx6.h>
It turns out that this module will not build with a kernel
based on 3.14.38_6pq_ga which includes this commit:
commit c3ae4b04ea47e32a2d7a953fd7a3089c6e07701c
Author: Anson Huang <b20788@freescale.com>
Date: Mon Apr 13 14:13:17 2015 +0800
MLK-10788-2 ARM: imx: rename busfreq from imx6 to imx
As busfreq need to cover both i.MX6 and i.MX7
and maybe later SoCs, so better to change the
name to support common imx SoC.
Signed-off-by: Anson Huang <b20788@freescale.com>
I received this error with both the off-the-shelf layers and
imx6qsabresd as well as the meta-fsl-arm-extra trying to build
the boundary devices with a newer kernel based on this branch.
At this point, it's not clear to me the best way to fix this.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next reply other threads:[~2015-10-05 21:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 21:18 Gary Thomas [this message]
2015-10-05 21:28 ` [meta-fsl-arm] Error in recent build Otavio Salvador
2015-10-05 22:00 ` Gary Thomas
2015-10-06 11:49 ` Otavio Salvador
2015-10-06 12:21 ` Gary Thomas
2015-10-06 12:24 ` Otavio Salvador
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=5612E93E.2050908@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=meta-freescale@yoctoproject.org \
/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.