From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
poky@lists.yoctoproject.org, Ross Burton <ross.burton@arm.com>,
Bill Mills <bill.mills@linaro.org>
Subject: Re: [poky] [PATCH] genericarm64.conf: override poky-altcfg distro kernel version
Date: Mon, 1 Dec 2025 13:28:19 +0200 [thread overview]
Message-ID: <aS1709XOUtEfZYwt@nuoska> (raw)
In-Reply-To: <CANNYZj-QJG6BU_F2vcvoD-PWBVHvgxseqf7LE72cqtu8HWxjfQ@mail.gmail.com>
Hi,
On Mon, Dec 01, 2025 at 11:47:46AM +0100, Alexander Kanavin wrote:
> On Mon, 1 Dec 2025 at 08:00, Mikko Rapeli via lists.yoctoproject.org
> <mikko.rapeli=linaro.org@lists.yoctoproject.org> wrote:
>
> > What kind of alternatives or different solutions do we have?
> > Another build variant in AB?
>
> Add the needed fixes to poky and the components used in it so that
> genericarm64 does not de facto require systemd? I find that deeply
> problematic to begin with.
We have a working configuration and we have plenty of broken ones.
I'm trying to serve users who would like to see the known
working configuration of systemd and latest stable kernel as output
from the Yocto Project. If something in that working configuration
breaks, then its up to me as co-maintainer of genericarm64 to fix it.
I'm sorry that this does not convince you. I've tried to help with
U-Boot, kernel etc genericarm64 BSP updates and IMO done quite a bit of
development work in linux-yocto kernel to get it working on more HW.
Sounds like building this genericarm64 "known good config" should
move to outside of oe-core and meta-yocto, maybe meta-arm then.
Cheers,
-Mikko
next prev parent reply other threads:[~2025-12-01 11:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-29 13:39 [PATCH] genericarm64.conf: override poky-altcfg distro kernel version Mikko Rapeli
2025-11-29 23:36 ` [poky] " Richard Purdie
2025-12-01 7:00 ` Mikko Rapeli
2025-12-01 10:47 ` Alexander Kanavin
2025-12-01 11:28 ` Mikko Rapeli [this message]
2025-12-01 11:39 ` Alexander Kanavin
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=aS1709XOUtEfZYwt@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=alex.kanavin@gmail.com \
--cc=bill.mills@linaro.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 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.