From: Otavio Salvador <otavio.salvador@ossystems.com.br>
To: Ken Davidson <ken.davidson@pobox.com>
Cc: meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] meta-imx issue with Hardknott #hardknott
Date: Mon, 3 Jan 2022 13:38:47 -0300 [thread overview]
Message-ID: <CAP9ODKryy74W2LmoKtwJMHLhnRZ14TK5N0=uv4zkaxqnH3BiDg@mail.gmail.com> (raw)
In-Reply-To: <sc3O.1639779513938524580.sqYz@lists.yoctoproject.org>
Hello Ken,
Em sex., 17 de dez. de 2021 às 19:18, Ken Davidson
<ken.davidson@pobox.com> escreveu:
> There is no subgroup for meta-imx, so I'm guessing this one is the closest.
>
> I'm trying to create a Hardknott version of Yocto for the i.MX 8M Mini board that we're using. The manufacturer (Congatec) only has code up to Zeus, so I'm starting with the Hardknott version of fsl-community-bsp and am trying to add in code from the manufacturer's Zeus implementation.
This is something which is expected to happen when you mix branches
... I'd suggest you to use meta-freescale and move to mainline
releases if it is supported. If it doesn't, you should contact
Congatec support and ask them.
> I've run into a problem with the Hardknott release of meta-imx. Under meta-bsp/recipes-bsp/u-boot, the u-boot-imx_2021.04.bb recipe is trying to find u-boot-imx-common.inc. However, the only file present is u-boot-common.inc. This is true for all three Hardknott branches of meta-imx.
>
> The equivalent folder under meta-freescale does include the proper file. Is this a bug or am I missing something? Or should I be using only meta-freescale and abandon meta-imx?
We try to be as close as possible to meta-imx; eventually they diverge
when NXP does new releases but they are pretty close nowadays.
--
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
prev parent reply other threads:[~2022-01-03 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 22:18 meta-imx issue with Hardknott #hardknott Ken Davidson
2022-01-03 16:38 ` Otavio Salvador [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='CAP9ODKryy74W2LmoKtwJMHLhnRZ14TK5N0=uv4zkaxqnH3BiDg@mail.gmail.com' \
--to=otavio.salvador@ossystems.com.br \
--cc=ken.davidson@pobox.com \
--cc=meta-freescale@lists.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 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).