From: Andrey Zhizhikin <andrey.z@gmail.com>
To: "Константин Еременок" <eremenok.k.by@gmail.com>
Cc: meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] Comunity vs i.MX #yocto
Date: Thu, 23 Jun 2022 20:52:34 +0200 [thread overview]
Message-ID: <CAHtQpK4vJvOOgeUOidKjtkfbfp+PH6+NV_20NLrzBGS-1a+zGA@mail.gmail.com> (raw)
In-Reply-To: <8K4p.1656006095146090784.Hj3E@lists.yoctoproject.org>
Hello Konstantin,
On Thu, Jun 23, 2022 at 7:41 PM Константин Еременок
<eremenok.k.by@gmail.com> wrote:
>
> Hi there.
> I have not followed Yocto iMX for some time.
> Today I found in the document "i.MX Yocto Project User's Guide" from NXP such text:
>
> "i.MX joined the Yocto Project community providing a release based on the Yocto Project framework."
>
> 1. Did I understand correctly: the war Community VS iMX is finished?
AFAIK, there was no war declared, not at least that I was aware of
when I started using Yocto Project and `meta-freescale` layer. ;-)
NXP is lacking a bit in pace to catch up with latest Yocto Project
releases when the do release their BSP, but overall - it is pretty
much aligned.
If there is a track record of this "war declaration", then I guess it
would be interesting for community to see it once you share it. :-)
> 2. Why here http://freescale.github.io development is stopped on "2.4 - codename Rocko:" version
This is maintained by Otavio IIRC, and perhaps it is a bit
"out-of-sync" with the current Documentation, which is available at
[1]. I guess it would be updated someday to reflect the current state
of development.
>
> Thank you.
>
>
--
Regards,
Andrey.
Link: [1]: https://github.com/Freescale/Documentation
next prev parent reply other threads:[~2022-06-23 18:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 17:41 Comunity vs i.MX #yocto Константин Еременок
2022-06-23 18:52 ` Andrey Zhizhikin [this message]
2022-06-23 18:53 ` [meta-freescale] " 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=CAHtQpK4vJvOOgeUOidKjtkfbfp+PH6+NV_20NLrzBGS-1a+zGA@mail.gmail.com \
--to=andrey.z@gmail.com \
--cc=eremenok.k.by@gmail.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 NNTP newsgroup(s).