Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Nora Schiffer <nora.schiffer@ew.tq-group.com>,
	 openembedded-core@lists.openembedded.org
Cc: oss@ew.tq-group.com
Subject: Re: [OE-core] [PATCH v2 1/3] kernel-uboot: move FIT_KERNEL_COMP_ALG to image-fitimage.conf
Date: Thu, 30 Jul 2026 14:09:58 +0100	[thread overview]
Message-ID: <d446f5a1d61eb3b5e9c832e8bc717bb869ba8ceb.camel@linuxfoundation.org> (raw)
In-Reply-To: <b0b1e1501a23b315704c5a6ef99a2c826408a56c.camel@ew.tq-group.com>

On Thu, 2026-07-30 at 13:15 +0200, Nora Schiffer wrote:
> On Thu, 2026-07-30 at 11:43 +0100, Richard Purdie wrote:
> 
> Okay, new plan: Change uboot_prep_kimage to accept the compression algorithm as
> an argument, so we can use different variables when calling it from kernel-
> uimage.bbclass and kernel-fit-extra-artifacts.bbclass. kernel-uimage.bbclass
> could then use a separate variable UBOOT_MKIMAGE_KERNEL_COMP_ALG instead of
> reusing the FIT one.
> 
> A more radical approach would be to skip the deprecation of using a linux.bin
> generated by the kernel recipe as a FIT image's kernel and drop support
> immediately.

Can you see from the commit history who might have been using that? Do
you think there are many people relying upon it? If that functionality
doesn't make much sense and wouldn't or shouldn't be used by people,
I'm fine with actually removing it, as long as we're clear about why it
likely isn't needed or is inefficient (or whatever) and what the
alternative is.

A lot of the time I think we support too many code paths when we should
try and encourage people to do the "best" known things.

Cheers,

Richard


  reply	other threads:[~2026-07-30 13:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-27  9:05 [PATCH v2 0/3] kernel-fit-image: allow replacing kernel, handle compression in FIT recipe Nora Schiffer
2026-07-27  9:05 ` [PATCH v2 1/3] kernel-uboot: move FIT_KERNEL_COMP_ALG to image-fitimage.conf Nora Schiffer
2026-07-30 10:43   ` [OE-core] " Richard Purdie
2026-07-30 11:15     ` Nora Schiffer
2026-07-30 13:09       ` Richard Purdie [this message]
2026-07-30 13:35         ` Nora Schiffer
2026-07-30 13:50           ` Richard Purdie
2026-07-30 14:05             ` Nora Schiffer
2026-07-27  9:06 ` [PATCH v2 2/3] kernel-fit-image: reintroduce option to replace kernel image Nora Schiffer
2026-07-27  9:06 ` [PATCH v2 3/3] kernel-fit-extra-artifacts: skip building linux.bin if unneeded Nora Schiffer

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=d446f5a1d61eb3b5e9c832e8bc717bb869ba8ceb.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=nora.schiffer@ew.tq-group.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=oss@ew.tq-group.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