From: <Marco.Cardellini@microchip.com>
To: <patrick@stwcx.xyz>
Cc: Hakim.Cherif@microchip.com, openbmc@lists.ozlabs.org,
Marco.Cardellini@microchip.com
Subject: RE: FW: OpenBMC support for SAM9X75 - follow up
Date: Tue, 7 Nov 2023 09:05:34 +0000 [thread overview]
Message-ID: <PH0PR11MB506228485FF916211F211F419EA9A@PH0PR11MB5062.namprd11.prod.outlook.com> (raw)
In-Reply-To: <ZUlxgh-hMJXl_LMe@heinlein.vulture-banana.ts.net>
Hi Patrick,
Many thanks for your feed back
I will discuss now with our Linux
Regards
Marco
Marco Cardellini
Manager-Applications Engineering
Tel: (+33) (0) 6 72 86 84 83
marco.cardellini@microchip.com
Microchip Technology Rousset
57 Avenue Victoire, 13790 Rousset, France
Fax: (+33) (0) 4 42 53 60 01
www.microchip.com
-----Original Message-----
From: Patrick Williams <patrick@stwcx.xyz>
Sent: Tuesday, November 7, 2023 12:07 AM
To: Marco Cardellini - M43165 <Marco.Cardellini@microchip.com>
Cc: geissonator@gmail.com; openbmc@lists.ozlabs.org; Hakim Cherif - M69710 <Hakim.Cherif@microchip.com>
Subject: Re: FW: OpenBMC support for SAM9X75 - follow up
On Fri, Nov 03, 2023 at 08:37:55AM +0000, Marco.Cardellini@microchip.com wrote:
> Hi Patrick, Andrew
>
> Many thanks for your feed back but we are not sure to understand your answer.
> .
> Does it mean openBMC team will keep updating their code based on any yocto release?
OpenBMC only does development against the Yocto master branch.
If you look at our Kirkstone branch you will see it is 3592 commits behind master and was last touched in April 2022. That means it is missing 1.5 years worth of BMC code development.
https://github.com/openbmc/openbmc/tree/kirkstone/meta-phosphor
>
> Checked the wiki, kirkstone is the latest LTS version of yocto.
> https://wiki.yoctoproject.org/wiki/Releases
LTS releases mean very little for OpenBMC. Most OpenBMC uses take a "live at HEAD" approach (or something very near to it). We do not maintain past releases and we certainly do not add new code to them.
>
> Did openBMC team mean if we want to put our meta (meta-atmel) to openBMC github, we have to follow every version from yocto release?
There are two approaches:
1. You add the bare minimum of meta-atmel recipes to support your SOC into our tree (this was Andrew G.'s suggestion). We need to understand what these recipes are. You will probably end up with a similar set as what is currently in meta-nuvoton.
2. You ensure your own meta-atmel is a well-maintained Yocto meta layer (by ensuring it always works against Yocto's master release as well) and then we can add it into our subtree import tool. This is how we keep meta-arm, meta-raspberrypi, meta-openembedded, etc. updated.
> Is there any quick way if we integrate our meta to kirkstone branch?
No. And even if we did, it would provide no value since our Kirkstone branch is using relatively ancient code.
--
Patrick Williams
prev parent reply other threads:[~2023-11-10 2:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BYAPR11MB35910AD28FB4793C988DFFB5F3DDA@BYAPR11MB3591.namprd11.prod.outlook.com>
[not found] ` <IA1PR11MB79188B3F91CABC644F5A9DC6ECDDA@IA1PR11MB7918.namprd11.prod.outlook.com>
[not found] ` <SJ0PR11MB50569E6F6F8B45AD0D85968E98DDA@SJ0PR11MB5056.namprd11.prod.outlook.com>
[not found] ` <DM4PR11MB54708C439647F1FA0BD581CAEEDDA@DM4PR11MB5470.namprd11.prod.outlook.com>
[not found] ` <SJ0PR11MB50567D3668198D7E85171D4198DDA@SJ0PR11MB5056.namprd11.prod.outlook.com>
[not found] ` <DM4PR11MB5470CEBF6C42DB3555269FD5EEDDA@DM4PR11MB5470.namprd11.prod.outlook.com>
[not found] ` <SJ0PR11MB5056283972C71AD9B030327F98DDA@SJ0PR11MB5056.namprd11.prod.outlook.com>
[not found] ` <DM4PR11MB54700AF4648C4A892E0DE879EEDDA@DM4PR11MB5470.namprd11.prod.outlook.com>
[not found] ` <IA1PR11MB7918002DB77F28F1D584A232ECDDA@IA1PR11MB7918.namprd11.prod.outlook.com>
[not found] ` <DM4PR11MB54704F112382D43BDFC2F898EEDCA@DM4PR11MB5470.namprd11.prod.outlook.com>
[not found] ` <PH0PR11MB5062973F2689347ACBB44B369EA0A@PH0PR11MB5062.namprd11.prod.outlook.com>
[not found] ` <DM4PR11MB547038DD545F8C702FA6011BEEA7A@DM4PR11MB5470.namprd11.prod.outlook.com>
[not found] ` <PH0PR11MB50623E55C582689F9A7336199EA6A@PH0PR11MB5062.namprd11.prod.outlook.com>
[not found] ` <DM4PR11MB5470969CC94F9A219F5DFF9DEEA5A@DM4PR11MB5470.namprd11.prod.outlook.com>
[not found] ` <PH0PR11MB50621C4604EFE68563B3E8069EA5A@PH0PR11MB5062.namprd11.prod.outlook.com>
2023-11-03 8:37 ` FW: OpenBMC support for SAM9X75 - follow up Marco.Cardellini
2023-11-06 23:06 ` Patrick Williams
2023-11-07 9:05 ` Marco.Cardellini [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=PH0PR11MB506228485FF916211F211F419EA9A@PH0PR11MB5062.namprd11.prod.outlook.com \
--to=marco.cardellini@microchip.com \
--cc=Hakim.Cherif@microchip.com \
--cc=openbmc@lists.ozlabs.org \
--cc=patrick@stwcx.xyz \
/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).