From: Patrick Williams <patrick@stwcx.xyz>
To: Andrew Geissler <geissonator@gmail.com>
Cc: openbmc@lists.ozlabs.org, Hakim.Cherif@microchip.com
Subject: Re: Documentation/Guidance in order to support another hardware
Date: Wed, 1 Nov 2023 09:30:57 -0500 [thread overview]
Message-ID: <ZUJhITh0f6o1zuzo@heinlein.vulture-banana.ts.net> (raw)
In-Reply-To: <445D6672-5358-494E-9163-5B4F91148971@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]
On Wed, Nov 01, 2023 at 07:19:50AM -0600, Andrew Geissler wrote:
> > On Oct 31, 2023, at 4:40 AM, <Hakim.Cherif@microchip.com> <Hakim.Cherif@microchip.com> wrote:
> >
> > To give you more details, we already have our own meta-layer that is meta-atmel :
> >
> > https://github.com/linux4sam/meta-atmel/tree/kirkstone
>
>
> I’m not sure what we’d do here. We run some scripts periodically to import other meta layers
> Like meta-openembedded, poky, meta-arm, … so in theory we could add this too but
> It may be better for you to just create what you need directly in openbmc under a new
> meta-microchip directory.
Since meta-atmel is using Kirkstone, there is absolutely no way we can
import this into our tree as a sub-tree like we do with meta-OE, etc.
We need to have confidence that the trees we import are going to keep in
line with upstream Yocto releases.
There appears to be a `master` branch in this repo. But, since the
LAYERSERIES_COMPAT doesn't include "nanbield", I'm not convinced it is
actually aligned with Yocto's master.
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-11-01 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 10:40 Documentation/Guidance in order to support another hardware Hakim.Cherif
2023-11-01 13:19 ` Andrew Geissler
2023-11-01 14:30 ` Patrick Williams [this message]
2023-11-01 14:27 ` Patrick Williams
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=ZUJhITh0f6o1zuzo@heinlein.vulture-banana.ts.net \
--to=patrick@stwcx.xyz \
--cc=Hakim.Cherif@microchip.com \
--cc=geissonator@gmail.com \
--cc=openbmc@lists.ozlabs.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).