From: <mike.looijmans@topic.nl>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] meta: uboot-config: Fix broken menuconfig for "fitImage" kernel
Date: Wed, 22 May 2024 07:28:53 +0200 [thread overview]
Message-ID: <023cbca2-b5e4-420c-b109-445d7d8480a4@topic.nl> (raw)
In-Reply-To: <5340825db3c98197e448c58b88381562edbed66f.camel@linuxfoundation.org>
On 21-05-2024 16:51, Richard Purdie wrote:
> On Tue, 2024-05-21 at 15:57 +0200, Mike Looijmans via lists.openembedded.org wrote:
>> kernel-fitimage inherited uboot-config, which resulted in failure to
>> run "menuconfig" on a system that has both multiple u-boot configs and
>> wants a fitImage kernel.
>>
>> Fix the issue by splitting up uboot-config into uboot-config-vars that
>> only contains the "harmless" variable settings, and inherit that in a
>> new uboot-config class which contains the Python code to do the U-boot
>> specific settings. Inherit only uboot-config-vars in kernel-fitimage
>> so that it has what it needs but doesn't break.
>>
>> Fixes: f9e834e31788 "meta: introduce KCONFIG_CONFIG_ENABLE_MENUCONFIG"
>> Signed-off-by: Mike Looijmans <mike.looijmans@topic.nl>
>> ---
>> meta/classes-recipe/kernel-fitimage.bbclass | 2 +-
>> meta/classes-recipe/uboot-config-vars.bbclass | 95 +++++++++++++++++++
>> meta/classes-recipe/uboot-config.bbclass | 80 +---------------
>> 3 files changed, 97 insertions(+), 80 deletions(-)
>> create mode 100644 meta/classes-recipe/uboot-config-vars.bbclass
>
> This looks like it might be a good candidate to move to a file in
> meta/conf rather than a new class file?
What does "this" refer to exactly?
Note that this patch just moves code, it doesn't introduce anything new.
> We could add any functions needed to lib/oe/ if they can be made
> suitably generic.
What "functions" would that be?
M.
--
Mike Looijmans
System Expert
TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands
T: +31 (0) 499 33 69 69
E: mike.looijmans@topic.nl
W: www.topic.nl
next prev parent reply other threads:[~2024-05-22 5:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.949ef384-8293-46b8-903f-40a477c056ae.cc544a93-e646-4932-8496-82717a21cde8@emailsignatures365.codetwo.com>
2024-05-21 13:57 ` [PATCH] meta: uboot-config: Fix broken menuconfig for "fitImage" kernel Mike Looijmans
2024-05-21 14:51 ` [OE-core] " Richard Purdie
2024-05-22 5:28 ` mike.looijmans [this message]
2024-05-22 5:39 ` Richard Purdie
2024-05-22 6:43 ` mike.looijmans
2024-05-23 13:43 ` Quentin Schulz
2024-05-24 10:03 ` mike.looijmans
2024-05-24 10:22 ` Richard Purdie
2024-05-28 5:20 ` mike.looijmans
2024-05-28 10:01 ` Quentin Schulz
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=023cbca2-b5e4-420c-b109-445d7d8480a4@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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