From: Andrey Zhizhikin <andrey.z@gmail.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: poberauer@yahoo.co.uk, meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] imx8qxp-mek-dom0.dtb - No rule to make target 'arch/arm64/boot/dts/freescale/imx8qxp-mek-dom0.dtb' #meta-freescale #imx8qxp
Date: Wed, 9 Nov 2022 17:05:04 +0100 [thread overview]
Message-ID: <CAHtQpK7+ZN5U79UKFuu_eZ_Rv8OP-K+Tiy3g+g_JrMoA+YPZ3w@mail.gmail.com> (raw)
In-Reply-To: <CAP9ODKopdykTFN6U2z2ihVukFD27Nj+hj_pgPihSmEAZJrp2aw@mail.gmail.com>
Hello all,
On Wed, Nov 9, 2022 at 4:37 PM Otavio Salvador
<otavio.salvador@ossystems.com.br> wrote:
>
>
>
> Em qua., 9 de nov. de 2022 às 11:59, Peter via lists.yoctoproject.org <poberauer=yahoo.co.uk@lists.yoctoproject.org> escreveu:
>>
>> We are creating a BSP for our i.MX 8X (i.MX 8QuadXPlus) based product.
>> To start, we are trying to build an existing BSP as a point of reference.
>> Have followed the instructions here:
>> https://github.com/Freescale/fsl-community-bsp-platform
>> But am getting:
>> | make[1]: *** No rule to make target 'arch/arm64/boot/dts/freescale/imx8qxp-mek-dom0.dtb'. Stop.
>> | make: *** [/workdir/fsl-community-bsp/build/tmp/work-shared/imx8qxp-mek/kernel-source/Makefile:1425: freescale/imx8qxp-mek-dom0.dtb] Error 2
>>
>> i.e.
>> repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b kirkstone
>> repo sync
>> MACHINE=imx8qxp-mek DISTRO=fslc-wayland source setup-environment build
>> bitbake core-image-minimal
>>
>> bitbake -e | grep PREFERRED_PROVIDER_virtual/kernel
>> gives
>> PREFERRED_PROVIDER_virtual/kernel="linux-fslc-imx"
>>
>> changing local.conf to
>> PREFERRED_PROVIDER_virtual/kernel="linux-imx"
>> (and deleting tmp) produces the same error
>>
>> Am I doing something wrong, or is this a bug?
>> Which combination of MACHINE, DISTRO, image, provider is a known working starting point for i.MX 8X (i.MX 8QuadXPlus) please?
>
>
> Looks like a bug. Please open an issue on GitHub.
Indeed it is! While machine file [1] shows that the DTB shall be
available, it is not present in the Kernel source tree [2]. Guess the
machine needs to be aligned with what is provided in the Kernel, as it
was not touched since 2021.
>
> --
> 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
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#24885): https://lists.yoctoproject.org/g/meta-freescale/message/24885
> Mute This Topic: https://lists.yoctoproject.org/mt/94914335/3617192
> Mute #meta-freescale:https://lists.yoctoproject.org/g/meta-freescale/mutehashtag/meta-freescale
> Mute #imx8qxp:https://lists.yoctoproject.org/g/meta-freescale/mutehashtag/imx8qxp
> Group Owner: meta-freescale+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/meta-freescale/unsub [andrey.z@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
Link: [1]: https://github.com/Freescale/meta-freescale/blob/66d738d4ab1270c2e87f5afabc085bdff205e5ac/conf/machine/imx8qxp-mek.conf#L12
Link: [2]: https://github.com/Freescale/linux-fslc/tree/5.15-2.1.x-imx/arch/arm64/boot/dts/freescale/
--
Regards,
Andrey.
prev parent reply other threads:[~2022-11-09 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 14:59 imx8qxp-mek-dom0.dtb - No rule to make target 'arch/arm64/boot/dts/freescale/imx8qxp-mek-dom0.dtb' #meta-freescale #imx8qxp Peter
2022-11-09 15:37 ` [meta-freescale] " Otavio Salvador
2022-11-09 16:03 ` imx8qxp-mek-dom0.dtb - No rule to make target 'arch/arm64/boot/dts/freescale/imx8qxp-mek-dom0.dtb' #meta-freescale Peter
2022-11-09 16:05 ` Andrey Zhizhikin [this message]
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=CAHtQpK7+ZN5U79UKFuu_eZ_Rv8OP-K+Tiy3g+g_JrMoA+YPZ3w@mail.gmail.com \
--to=andrey.z@gmail.com \
--cc=meta-freescale@lists.yoctoproject.org \
--cc=otavio.salvador@ossystems.com.br \
--cc=poberauer@yahoo.co.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).