From: "Robert Berger" <robert.berger.yocto.user@gmail.com>
To: amaya jindal <amayajindal786@gmail.com>,
yocto <yocto@yoctoproject.org>,
yocto@lists.yoctoproject.org
Subject: Re: [yocto] Points to consider while moving to new yocto versions
Date: Mon, 25 Jan 2021 14:46:12 +0200 [thread overview]
Message-ID: <dfbc9dbd-7fc9-ce3e-ac4e-261f1b6380e6@gmail.com> (raw)
In-Reply-To: <CAHXFBWsgp+B1kt_vq2N1+pS0WMQifz-vFg9xPzNsokhiJz8Weg@mail.gmail.com>
Hi,
My comments are in-line
On 25/01/2021 10:07, amaya jindal wrote:
> Hi All,
>
> We are planning to move to New yocto from current one that is krogoth
> yocto to some updated one.
I would consider it "best practice" to somewhat try to stay up to date
with recent yocto versions and plan for this from the beginning of your
project.
What I mean is to have a "stable release" and a "next release" which is
being used in your nightly builds and tests.
This will make it significantly easier to make version upgrades.
> We are not thinking to move to gates-garth or
> some other major release but the releases than can have easily support
> for arm.
I am not sure what you mean by that?
Which versions make it easier/more difficult to support arm?
It's more a question of which chip/kernel/boot loader,...
>
> Please support and help.
>
> Points need to take care to port to new yocto version.
Ssince you use a completely outdated and end of life version[1] it might
require quite some effort to update, but through pain we learn ;)
[1] https://wiki.yoctoproject.org/wiki/Releases
Which chip do you use?
Is it supported by an upstream kernel/boot loader?
Which (additional) layers do you use?
Are these layers supported by the same version as the Yocto version you
want to move to?
How about your own recipes?
Are they compatible with upstream yocto?
>
> Regards,
> Rohit
Regards,
Robert
>
>
>
>
next prev parent reply other threads:[~2021-01-25 12:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 8:07 Points to consider while moving to new yocto versions amaya jindal
2021-01-25 9:24 ` [yocto] " Erik Boto
2021-01-25 12:46 ` Robert Berger [this message]
2021-01-27 9:08 ` amaya jindal
2021-01-27 10:10 ` Martin Jansa
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=dfbc9dbd-7fc9-ce3e-ac4e-261f1b6380e6@gmail.com \
--to=robert.berger.yocto.user@gmail.com \
--cc=amayajindal786@gmail.com \
--cc=yocto@lists.yoctoproject.org \
--cc=yocto@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.