public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	Ross Burton <ross.burton@arm.com>,
	poky@lists.yoctoproject.org,
	openembedded-core@lists.openembedded.org,
	openembedded-architecture@lists.openembedded.org
Subject: Re: [Openembedded-architecture] [RFC PATCH] Add genericarm64 MACHINE using upstream defconfig
Date: Wed, 21 Feb 2024 16:10:10 +0200	[thread overview]
Message-ID: <ZdYEQreQHV4RMjiE@nuoska> (raw)
In-Reply-To: <17B5E38E239794A0.12054@lists.openembedded.org>

Hi,

On Wed, Feb 21, 2024 at 03:23:48PM +0200, Mikko Rapeli via lists.openembedded.org wrote:
> FWIW, we have been using upstream kernel.org aarch64 defconfig plus
> few board specific fragments and few extra features for our testing needs.
> I have been very happy that several major kernel version updates have already
> been done this way and zero adaptations needed on our side for the
> ARM SystemReady boards and firmware which we support. A simple CI run to show
> passing test results was sufficient for a poky update with new kernel
> major version.
> 
> The implementation here looks pretty much like ours. Looks good, thanks Ross!
>
> More details of our setup:
> 
> https://gitlab.com/Linaro/trustedsubstrate/meta-ledge-secure/-/blob/main/meta-ledge-secure/recipes-kernel/linux/linux-ledge-common.inc?ref_type=heads
> https://gitlab.com/Linaro/trustedsubstrate/meta-ledge-secure/-/tree/main/meta-ledge-secure/recipes-kernel/linux/ledgearm64-kmeta?ref_type=heads
> https://trs.readthedocs.io/en/latest/

Our machine is based on poky qemuarm64 machine and thus uses KBRANCH:qemuarm64 so
I don't see a need for new branch from linux-yocto recipe maintainer.
https://git.yoctoproject.org/linux-yocto/log/?h=v6.5/standard/qemuarm64

But maybe I don't see the full picture.

Cheers,

-Mikko


  parent reply	other threads:[~2024-02-21 14:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-21 10:57 [RFC PATCH] Add genericarm64 MACHINE using upstream defconfig ross.burton
2024-02-21 11:03 ` Patchtest results for " patchtest
2024-02-21 11:21 ` [Openembedded-architecture] " Richard Purdie
2024-02-21 13:23   ` Mikko Rapeli
     [not found]   ` <17B5E38E239794A0.12054@lists.openembedded.org>
2024-02-21 14:10     ` Mikko Rapeli [this message]
2024-02-21 16:15   ` Anton Antonov
2024-02-21 16:47     ` [OE-core] " Richard Purdie
2024-02-21 13:33 ` Bruce Ashfield
     [not found] ` <17B5E41BBD3629FA.11907@lists.openembedded.org>
2024-02-21 13:37   ` [OE-core] " Bruce Ashfield
2024-02-21 15:06 ` Paul Barker
2024-02-22  3:21   ` [poky] " Mark Hatle
2024-02-21 19:29 ` paulg

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=ZdYEQreQHV4RMjiE@nuoska \
    --to=mikko.rapeli@linaro.org \
    --cc=openembedded-architecture@lists.openembedded.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=poky@lists.yoctoproject.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=ross.burton@arm.com \
    /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