All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: meta-freescale@yoctoproject.org
Subject: Re: [meta-fsl-arm] Error in recent build
Date: Tue, 6 Oct 2015 06:21:45 -0600	[thread overview]
Message-ID: <5613BCD9.8020004@mlbassoc.com> (raw)
In-Reply-To: <CAP9ODKp3nLf3D5TX0zUv0gpNAW1rv-Joadxzd8nzvUs59E_orQ@mail.gmail.com>

On 2015-10-06 05:49, Otavio Salvador wrote:
> On Mon, Oct 5, 2015 at 7:00 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>> On 2015-10-05 15:28, Otavio Salvador wrote:
>>>
>>> On Mon, Oct 5, 2015 at 6:18 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>>>>
>>>> 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.
>>>
>>>
>>> Agreed;  I think the easiest way is to backport this commit for
>>> linux-fslc fork and get out of the patch in the module.
>>>
>>> Would you be willing to help to do this?
>>
>> Sure, I can look at it (I'm mostly interested in the linux-boundary
>> recipe, but I'll see if I can find a good/extensible solution for
>> all kernels).  Any particular recipe I should look at [first]?
>
> I would backport this to the linux-fslc 3.14-1.0.x-mx6 which offers
> fixes on top of the 3.14.28 GA kernel. Once we do that, we can put the
> same patches on the other kernels if need.
>

Couldn't the patch for kernel-module-imx-gpu-viv just be adjusted for 3.14.38?
Right now, it tests for
   #elif LINUX_VERSION_CODE < KERNEL_VERSION(3, 15, 0)
why not change it to
   #elif LINUX_VERSION_CODE < KERNEL_VERSION(3, 14, 38)

It seems that the change of busfreq-imx6.h => busfreq-imx.h happened before 3.14.38

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  reply	other threads:[~2015-10-06 12:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-05 21:18 [meta-fsl-arm] Error in recent build Gary Thomas
2015-10-05 21:28 ` Otavio Salvador
2015-10-05 22:00   ` Gary Thomas
2015-10-06 11:49     ` Otavio Salvador
2015-10-06 12:21       ` Gary Thomas [this message]
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=5613BCD9.8020004@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.